> Generally, the install process should respect the prefix (ie. /usr in > your case, /usr/local in the default case) and then choose the > appropriate library directories below that (ie. /usr/lib, /usr/lib64 in > your case), but I can't find anything obvious in the README about > specifying architecture-dependent install directories.
Well that's pretty much what's happening ... either the 64bit libs aren't being put in /usr/lib64 ... they're all being put in /usr/lib or they were never compiled up in 64bit mode. The only think I can think of is that the configure script doesn't check the mode the OS is running in and take appropriate steps, ie.e compile the libs in both 32 and 64 bit mode and place them accordingly. I know this is a problem because when I try and compile up mod_python it's telling I'm getting the following error when it tries to link libpython2.4.a : /usr/bin/ld: /usr/lib/python2.4/config/libpython2.4.a(abstract.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/python2.4/config/libpython2.4.a: could not read symbols: Bad value Which basically means to me that for whatever reason, when python compiled up, the ./configure script didn't see that the os was running in 64bit mode and compile the libraries in PIC mode, something I think that is required for libraries on a 64bit OS. Respectfully, Christopher Taylor -- http://mail.python.org/mailman/listinfo/python-list
