gcc segmentation fault (signal 11 ) while compiling brotli on Cygwin AppVeyor CI i686 environment

Lemures Lemniscati lemures.lemniscati@gmail.com
Sat Oct 10 02:40:41 GMT 2020


I'm preparing brotli-1.0.9-1 packages, which are successfully built and packaged on my local machine.

Being tested on Cygwin AppVeyor CI, it goes successfully on x86_64,
but it fails on i686 because gcc gets a signal 11.

1056	brotli	failed	Lemures Lemniscati	3faae22b	playground	[log]	x86 x86_64	2020-10-10 01:15:00	840
  commit: https://cygwin.com/git/?p=git/cygwin-packages/brotli.git;a=commitdiff;h=3faae22bbc77cda37858df432a4404c7c624c1a6
  log: https://ci.appveyor.com/project/cygwin/scallywag/builds/35671931

1055	brotli	failed	Lemures Lemniscati	29237950	playground	[log]	x86 x86_64	2020-10-10 00:56:00	840
  commit: https://cygwin.com/git/?p=git/cygwin-packages/brotli.git;a=commitdiff;h=29237950d0eb5cadca0671e4710d497317ef41eb
  log: https://ci.appveyor.com/project/cygwin/scallywag/builds/35671826

Differnce of the cygport files is just a line `uname -a` in src_compile(), so we would expect failures at same point.
But failure points are diffent.

In 1056, it fails at 'gcc ... -c python/_brotli.cc -o bin/temp.cygwin-3.1.7-i686-2.7/python/_brotli.o'

In 1055, it fails at 'gcc ... -c c/common/constants.c -o bin/temp.cygwin-3.1.7-i686-2.7/c/common/constants.o'

Currently, I have no idea how to solve this issue.

Although similar issue was reported in the past
  https://sourceware.org/legacy-ml/cygwin/2014-10/msg00552.html ,
there seems no essential solution found.

Because the packages have been built successfully on my local environment,
Can I ignore this failure?

Any help is welcome.
Thank you in advance.



More information about the Cygwin-apps mailing list