From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: gcc segmentation fault (signal 11 ) while compiling brotli on Cygwin AppVeyor CI i686 environment
Date: Sat, 10 Oct 2020 08:09:51 -0400 [thread overview]
Message-ID: <cd3b679f-ad66-ca17-38d7-3bb25b2192fc@cornell.edu> (raw)
In-Reply-To: <20201010114038.24F1.50F79699@gmail.com>
On 10/9/2020 10:40 PM, Lemures Lemniscati via Cygwin-apps wrote:
> 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
I've had this problem with several of my packages.
> Because the packages have been built successfully on my local environment,
> Can I ignore this failure?
That's what I've done.
Ken
next prev parent reply other threads:[~2020-10-10 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 2:40 Lemures Lemniscati
2020-10-10 12:09 ` Ken Brown [this message]
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=cd3b679f-ad66-ca17-38d7-3bb25b2192fc@cornell.edu \
--to=kbrown@cornell.edu \
--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).