I cannot get dev-python/mod_python-2.7.11 to build on my amd64 machine. I have to use apache-1.3, and therefore have to use mod_python-2.7 branch. But it is not keyworded for amd64. The build process is not fine, it require a patch for passing -fPIC: # ebuild mod_python-2.7.11.ebuild install ... Compiling for DSO. For static, do "make static" /usr/sbin/apxs -I/var/tmp/portage/mod_python-2.7.11/work/mod_python-2.7.11/src/include -I/usr/include/apache -I/usr/include/python2.3 -c mod_python.o _apachemodule.o requestobject.o tableobject.o util.o serverobject.o connobject.o -lm /usr/lib/python2.3/config/libpython2.3.a -lpthread -ldl -lutil -lm -L/lib64 -lz gcc -shared -o mod_python.so mod_python.o _apachemodule.o requestobject.o tableobject.o util.o serverobject.o connobject.o -lm /usr/lib/python2.3/config/libpython2.3.a -lpthread -ldl -lutil -lm -L/lib64 -lz -L/usr/lib -lm -lcrypt -ldb-4.2 -lmm -lexpat -lgdbm -lgdbm_compat -lpthread /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../../x86_64-pc-linux-gnu/bin/ld: mod_python.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC mod_python.o: could not read symbols: Bad value collect2: ld returned 1 exit status apxs:Break: Command failed with rc=1 make[1]: *** [mod_python.so] Error 1 make[1]: Leaving directory `/var/tmp/portage/mod_python-2.7.11/work/mod_python-2.7.11/src' make: *** [do_dso] Error 2 !!! ERROR: dev-python/mod_python-2.7.11 failed. !!! Function src_compile, Line 37, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Uhm? We can't add keywords to something that does not even compile...
I was just following this: There used to be issues with the lack of -fPIC being specified when building shared objects, the reasoning is in this mailing list post: Porting to Hammer -- scan down to "Shared libraries must be compiled with -fPIC". If you find any packages that complain about needing -fPIC to run/link properly, please notify us immediately, as we need to update that package. Please do not specify -fPIC in your global CFLAGS as that is not an acceptable solution and just a workaround. http://www.gentoo.org/proj/en/base/amd64/technotes/index.xml?part=1&chap=3#doc_chap9 Please fix this bug, thanks.
Which bug? mod_python-2.7.x is not marked amd64 at all. Reopen if you have a patch, otherwise this cannot be keyworded amd64 because it does not compile.
It was just a matter of adding -fPIC in the CFLAGS, this is done in 3.x branch of python. Attaching patch.
Created attachment 69085 [details, diff] patch Attaching patch
we're currently testing a new alias system, sorry for the bugspam
Why don't you try the current mod_python-3.2.5b, actually in few days upcoming 3.2 final release? It works excellent for me on x86, though.
(In reply to comment #7) > Why don't you try the current mod_python-3.2.5b, actually in few days upcoming > 3.2 final release? It works excellent for me on x86, though. > mod_python-3.x doesn't work with apache-1.3.x.
Try http://www.modpython.org/dist/mod_python-3.2.6.tgz
Compiles and works fine for me with the proposed patch. Since the package is only building a shared library and no executables simply adding -fPIC to the global CFLAGS seems acceptable to me...
thanks everybody, this is InCVS
