The long and short of all the problems I've been having lately seems to be this: 
python 2.3.3 gets built, but it's modules don't get built correctly, which is why 
python doesn't work and portage and .... etc. etc. 

I tried using mcpu=athlon-xp and -O2 instead of -O3 but the problem doesn't change.
I wander if it is the fault of the new glibc ?

These are the error messages I get in build:

unning build
running build_ext
building 'struct' extension
creating build
creating build/temp.linux-i686-2.3
gcc -pthread -DNDEBUG -march=athlon-xp -O2 -pipe -fomit-frame-pointer -fPIC 
-fno-strict-aliasing -I. -I/var/tmp/portage/python-2.3.3/work/Python-2.3.3/./Include 
-I/var/tmp/portage/python-2.3.3/work/Python-2.3.3/Include 
-I/var/tmp/portage/python-2.3.3/work/Python-2.3.3 -c 
/var/tmp/portage/python-2.3.3/work/Python-2.3.3/Modules/structmodule.c -o 
build/temp.linux-i686-2.3/structmodule.o
creating build/lib.linux-i686-2.3
gcc -pthread -shared build/temp.linux-i686-2.3/structmodule.o -L/usr/local/lib -o 
build/lib.linux-i686-2.3/struct.so
*** WARNING: importing extension "struct" failed with exceptions.AttributeError: 
'module' object has no attribute 'load_dynamic'

A quick google reveals a similar problem with python 2.3.3 on a totally different 
architecture:

http://mail.python.org/pipermail/python-bugs-list/2003-October/020521.html

Has anyone managed to build python 2.3.3 with athlon-xp and the new glibc ?

--  
Michele Alzetta

--
[EMAIL PROTECTED] mailing list

Reply via email to