This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gcc segfaults compiling python extensions

Hello CygWin maintainers,

I want to report an observation, which might help address a bug.

This issue has been reported in the past in:

I recently ran into the same issue:

On AppVeyor [] running Windows Server 2012 R2
With the latest available cygwin 32-bit

building a Python module for CygWin python (no Windows Python) causes
gcc to SIGSEGV (11)

gcc -fno-strict-aliasing -ggdb -O2 -pipe
-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
error: command 'gcc' terminated by signal 11
Running: ' build' failed

Also see:

As per: I switched
to Windows Server 2016 and this indeed does not show the same issue.

I've been tracking this in:

Hope to have sufficiently informed you.

Let me know if you need additional information.

Kind regards,

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]