Charles Solar added the comment:
Hello again, I got a copy of the latest python from the 2.7 branch, recompiled
with CFLAGS="-m64 -O3" and LDFLAGS="-m64" and my extension compiled just fine.
So I can verify this bug fixed
--
__
Charles Solar added the comment:
I just recompiled using your suggested flags and it is now properly linking my
extensions. I guess using CFLAGS and LDFLAGS was causing the problem.
Is specifying CC the recommended way to build 64 bit python? If so when I
guess this issue is not really an
New submission from Charles Solar :
On solaris, if you build a 64 bit python and use it to build an extension, it
will not properly link the module.
Apparently solaris requires the -m64 flag in the linker as well as the compile
steps. Python distutils successfully compiles all the object
Changes by Charles Solar :
Removed file: http://bugs.python.org/file17403/config.log
___
Python tracker
<http://bugs.python.org/issue8767>
___
___
Python-bugs-list mailin
Charles Solar added the comment:
Seems as though python 2.7 should not support --disable-unicode so this ticket
is invalid. I just googled python disable unicode, but it seems that the
decision to never disable unicode is recent.
Closing
--
status: open -> clo
New submission from Charles Solar :
I am compiling python on AIX 5.3. The normal configure and make works, except
it fails to compile the unicodedata module. The assembler reports a bunch of
these errors:
Error: value of 0001268b too large for field of 2 bytes at
006d
