From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: gcc segmentation fault (signal 11 ) while compiling brotli on Cygwin AppVeyor CI i686 environment
Date: Sat, 10 Oct 2020 11:40:41 +0900 [thread overview]
Message-ID: <20201010114038.24F1.50F79699@gmail.com> (raw)
Hi!
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.
https://cygwin.com/cgi-bin2/jobs.cgi
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'
https://ci.appveyor.com/project/cygwin/scallywag/builds/35671931/job/rro6vjdefpxyen3c
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'
https://ci.appveyor.com/project/cygwin/scallywag/builds/35671826/job/6cijsycw1n7qmumr
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.
Regards,
Lem
next reply other threads:[~2020-10-10 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 2:40 Lemures Lemniscati [this message]
2020-10-10 12:09 ` Ken Brown
2020-10-10 14:22 ` Lemures Lemniscati
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201010114038.24F1.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).