[mod_python] Debian 2.2 and mod_python

rafal polonski rafi at voruta.ek.univ.gda.pl
Wed Jan 17 17:33:51 EST 2001


Hello,
I am trying to run mod_python on Debian 2.2 distribution.

Apache 1.3.9
Python 1.5.2 (with threads)
mod_python-2.7.1
gcc 2.95

Compiling as a DSO module goes without any error.
Of course I get a warning about having Python compiled WITH threads.

apache -X 
gives me Segmentation fault:
[Wed Jan 17 16:48:01 2001] [notice] caught SIGTERM, shutting down]

So probably I have to blame Python compiled with threads.


So I downloaded Python 1.6, compiled it without threads but trying to
compile mod_python with this 1.6 version gives this error:
gcc -shared -o mod_python.so mod_python.o _apachemodule.o requestobject.o
tableo
bject.o util.o serverobject.o connobject.o -lm
/tmp/modp/Python-1.6/libpython1.6
.a -lieee -ldl -lm -lc -lm -lcrypt -ldb
/usr/bin/ld: mod_python.so: undefined versioned symbol name
_LIB_VERSION@@GLIBC_
2.0
/usr/bin/ld: failed to set dynamic section sizes: Bad value
collect2: ld returned 1 exit status
apxs:Break: Command failed with rc=65536
make[1]: *** [mod_python.so] Error 1
make[1]: Leaving directory `/tmp/modp/mod_python-2.7.1/src'
make: *** [do_dso] Error 2
# 


So I downloaded Python 2.0, compiled it without threads.
With this Python version Apache and mod_python started.
I got quiet huge .so file:
2873238 Jan 17 17:26 mod_python.so 
Stripped version: 1601536 Jan 17 17:28 mod_python.so
Is that normal?


So the question is:
Can I compile mod_python with threaded Python 1.5.2? or just forget 
about threaded vesrion and use one without them?
Why did I get problems trying to use 1.6 Python version wit mod_python?

habe a nice day
rafal



More information about the Mod_python mailing list