From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: BUG: gcc segfaults compiling python extensions
Date: Tue, 28 Oct 2014 17:10:00 -0000 [thread overview]
Message-ID: <544FCE0C.2030904@gmail.com> (raw)
In-Reply-To: <87oasw89eg.fsf@eve.fritz.box>
On 10/28/2014 5:08 PM, Florian Friesdorf wrote:
>
> Steps to reproduce:
>
> - 64bit Windows Server 2012 R2
>
> - cygwin 32bit 1.7.32 (also with 1.7.33 test release)
>
> - download, unpack, cd
> https://ftp.dlitz.net/pub/dlitz/crypto/pycrypto/pycrypto-2.6.1.tar.gz
>
> - python setup.py build
> ...
> building 'Crypto.Hash._MD2' extension
> creating build/temp.cygwin-1.7.33-i686-2.7
> creating build/temp.cygwin-1.7.33-i686-2.7/src
> gcc -fno-strict-aliasing -ggdb -pipe -Wimplicit-function-declaration -fdebug-prefix-map=/usr/src/ports/python/python-2.7.8-1.i686/build=/usr/src/debug/python-2.7.8-1 -fdebug-prefix-map=/usr/src/ports/python/python-2.7.8-1.i686/src/Python-2.7.8=/usr/src/debug/python-2.7.8-1 -fwrapv -Wall -Wstrict-prototypes -std=c99 -O3 -fomit-frame-pointer -Isrc/ -I/usr/include/python2.7 -c src/MD2.c -o build/temp.cygwin-1.7.33-i686-2.7/src/MD2.o
> gcc -shared -Wl,--enable-auto-image-base -L. build/temp.cygwin-1.7.33-i686-2.7/src/MD2.o -L/usr/lib/python2.7/config -L/usr/lib -lpython2.7 -o build/lib.cygwin-1.7.33-i686-2.7/Crypto/Hash/_MD2.dll
> error: command 'gcc' terminated by signal 11
>
> - rererun: python setup.py build
build find on W7-64 with cygwin32 bit
CYGWIN_NT-6.1-WOW64 1.7.32(0.274/5/3) 2014-08-13 23:03
$ find . -name *.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_AES.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_ARC2.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_ARC4.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_Blowfish.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_CAST.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_DES.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_DES3.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Cipher/_XOR.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Hash/_MD2.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Hash/_MD4.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Hash/_RIPEMD160.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Hash/_SHA224.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Hash/_SHA256.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Hash/_SHA384.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Hash/_SHA512.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/PublicKey/_fastmath.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Util/strxor.dll
./build/lib.cygwin-1.7.32-i686-2.7/Crypto/Util/_counter.dll
>
> regards
> Marko and Florian
BLODA ?
https://cygwin.com/acronyms/#BLODA
--
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 prev parent reply other threads:[~2014-10-28 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 16:08 Florian Friesdorf
2014-10-28 17:10 ` Marco Atzeri [this message]
2014-10-28 17:38 ` Florian Friesdorf
2014-10-29 11:03 ` Florian Friesdorf
2014-10-31 10:48 ` Florian Friesdorf
2014-12-08 15:16 ` Florian Friesdorf
2014-12-08 15:52 ` Corinna Vinschen
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=544FCE0C.2030904@gmail.com \
--to=marco.atzeri@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).