From: Joachim Metz <joachim.metz@gmail.com>
To: cygwin@cygwin.com
Subject: gcc segfaults compiling python extensions
Date: Fri, 18 Aug 2017 05:21:00 -0000 [thread overview]
Message-ID: <CAPq-Lw0SPYCyDqtpQE=bHOsOw2hnD-taZ+HLYOXZjSvsctpkjw@mail.gmail.com> (raw)
Hello CygWin maintainers,
I want to report an observation, which might help address a bug.
This issue has been reported in the past in:
https://cygwin.com/ml/cygwin/2014-10/msg00502.html
I recently ran into the same issue:
On AppVeyor [https://ci.appveyor.com/] running Windows Server 2012 R2
With the latest available cygwin 32-bit
[https://github.com/libyal/libfwnt/blob/master/appveyor.yml#L39]
building a Python module for CygWin python (no Windows Python) causes
gcc to SIGSEGV (11)
gcc -fno-strict-aliasing -ggdb -O2 -pipe
-Wimplicit-function-declaration
-fdebug-prefix-map=/usr/src/ports/python2/python2-2.7.13-1.i686/build=/usr/src/debug/python2-2.7.13-1
-fdebug-prefix-map=/usr/src/ports/python2/python2-2.7.13-1.i686/src/Python-2.7.13=/usr/src/debug/python2-2.7.13-1
-DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DHAVE_CONFIG_H=
-DLOCALEDIR="/usr/share/locale" -Iinclude -Icommon -Ilibcerror
-Ilibcthreads -Ilibcdata -Ilibcnotify -Ilibfwnt
-I/usr/include/python2.7 -c libcerror/libcerror_error.c -o
build/temp.cygwin-2.8.2-i686-2.7/libcerror/libcerror_error.o
error: command 'gcc' terminated by signal 11
Running: 'setup.py build' failed
Also see: https://ci.appveyor.com/project/joachimmetz/libfwnt/build/79/job/l1gqocdqoafax0k7
As per: https://cygwin.com/ml/cygwin/2014-10/msg00552.html I switched
to Windows Server 2016 and this indeed does not show the same issue.
I've been tracking this in: https://github.com/libyal/libyal/issues/34
Hope to have sufficiently informed you.
Let me know if you need additional information.
Kind regards,
Joachim
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2017-08-18 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 5:21 Joachim Metz [this message]
2017-08-18 13:09 ` cyg Simple
2017-08-23 19:38 Joachim Metz
2017-08-23 19:52 ` cyg Simple
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='CAPq-Lw0SPYCyDqtpQE=bHOsOw2hnD-taZ+HLYOXZjSvsctpkjw@mail.gmail.com' \
--to=joachim.metz@gmail.com \
--cc=cygwin@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).