Python 2.2.1 vs. gcc 3.1?
Andrew Koenig
ark at research.att.com
Fri Jun 7 13:47:37 EDT 2002
PPS: I tried building one of the .so files by hand, essentially by
snarfing the output from the Makefile log and executing it manually:
$ gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I. -I/tmp/build-python/Python-2.2.1/./Include -I/usr/local/include -IInclude/ -c /tmp/build-python/Python-2.2.1/Modules/structmodule.c -o build/temp.solaris-2.8-sun4u-2.2/structmodule.o
$ gcc -shared build/temp.solaris-2.8-sun4u-2.2/structmodule.o -L/usr/local/lib -o build/lib.solaris-2.8-sun4u-2.2/struct.so
$ ldd build/lib.solaris-2.8-sun4u-2.2/struct.so
libgcc_s.so.1 => /usr/gnu/lib/libgcc_s.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1
So apparently it is building a .so file with references correctly resolved.
How do I go about finding out the cause of the failure?
More information about the Python-list
mailing list