[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-02-16 Thread Takahiro Matsumoto
Takahiro Matsumoto added the comment: I could solve this with following procedures. - prepare binutil package under /somewhere/ (i.e. GNU ld, GNU as is available under /somewhere/bin/) - prepare your local gcc script below and set path for use. #!/bin/sh /your_path_to_gcc/gcc -B/somewhere/b

[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-01-09 Thread Martin v. Löwis
Martin v. Löwis added the comment: Ah, ok. ctypes can indeed only build with GNU tools. This is a known issue, and nobody has volunteered to fix it yet. Closing it as such, then. -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-01-09 Thread Aki
Aki added the comment: > I'm really puzzled; gcc would normally not generate assembler code like this. This is because an assembler source (sysv.S) was given. Python-2.6.1/Modules/_ctypes/libffi/src/x86/sysv.S It was created by Red Hat. A macro, RAW_CLOSURE_CIF_OFFSET, contains '~'.

[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-01-09 Thread Aki
Aki added the comment: I have installed GNU binutil package to my machine to use GNU as. I re-run configure but configure somehow always found Sun as rather than GNU as even I saw GNU as first from my csh environment. I temporalily renamed Sun as so that configure was forced to use GNU as. With

[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-01-09 Thread Martin v. Löwis
Martin v. Löwis added the comment: > movl 10 + 3) & ~3) + 4) + 4)(%eax), %edx I'm really puzzled; gcc would normally not generate assembler code like this. Instead, with the expression being constant, gcc should normally compute its result, and fill that into the assembler code. To study t

[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-01-09 Thread Aki
Aki added the comment: Hello Martin, Thank you for your prompt response. I recompiled the source with --save-temps. I examined the assembler source and found that it was complaining about '~'! movl 10 + 3) & ~3) + 4) + 4)(%eax), %edx ^ this one The source was compiled a

[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-01-09 Thread Martin v. Löwis
Martin v. Löwis added the comment: Run the gcc command line with --save-temps (-fsave-temps if the former doesn't work), and inspect the assembler file around the line where the assembler complains. Is this inline assembler code possibly? -- nosy: +loewis __

[issue4902] failed to build ctypes in Python2.6.1 (even with gcc)

2009-01-09 Thread Aki
New submission from Aki : I'm trying to build Python 2.6.1 on Solaris/x86 machine but it puked. gcc -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -I/home/neko/gnu/Python-2.6.1/./Include -Ibuild/temp.solaris-2.10-i86pc-2.6/libffi/include -Ibuild/temp.solaris-2.1