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
