[mod_python] Problems with -HEAD and Apache 2.0.40 on FreeBSD

I haven't tried it on FreeBSD yet. Apache seemed (or seemed, don't know if
it's resolved in .40) to have some sort of a problem with FreeBSD threads
(thus prefork being the default MPM). Because of this I actually moved all
my development to Linux (to my dismay). So it's possible you have to do
everything without threads. If you figre this out out, please let me know.

Grisha

On Sun, 1 Sep 2002, Gerhard [iso-8859-1] HДring wrote:

> I tried to get the CVS version working with Apache 2.0.40 on FreeBSD
> 4.6-STABLE but had no luck :-(
>
> This is what I did:
>
> compiled the FreeBSD apache2 port using WITH_THREADS=1. Which seems to
> have worked:
>
> gargamel# ldd /usr/local/sbin/httpd
> /usr/local/sbin/httpd:
> [...]
> libc_r.so.4 => /usr/lib/libc_r.so.4 (0x28225000)
> libc.so.4 => /usr/lib/libc.so.4 (0x282df000)
>
> I'm not sure if its ok to link against libc_r and libc at the same time,
> though. But as is, Apache seems to display static pages fine. But then,
> I have no experience with Apache2 whatsoever.
>
> gargamel# /usr/local/sbin/httpd -l
> Compiled in modules:
> core.c
> prefork.c
> http_core.c
> mod_so.c
>
> So it looks like it's using the preforked model.
>
> The Python compiled against is the standard FreeBSD port with threads
> enabled:
> gargamel# ldd /usr/local/bin/python
> /usr/local/bin/python:
> libutil.so.3 => /usr/lib/libutil.so.3 (0x280e6000)
> libm.so.2 => /usr/lib/libm.so.2 (0x280ef000)
> libc_r.so.4 => /usr/lib/libc_r.so.4 (0x2810b000)
>
> mod_python.so is statically linked against libpython2.2.a, however again
> is linked against the normal, nonthreaded libc (!):
>
> gargamel# ldd /usr/local/libexec/apache2/mod_python.so
> /usr/local/libexec/apache2/mod_python.so:
> libm.so.2 => /usr/lib/libm.so.2 (0x281d9000)
> libutil.so.3 => /usr/lib/libutil.so.3 (0x281f5000)
> libc.so.4 => /usr/lib/libc.so.4 (0x28069000)
>
> Needless to say, the results aren't that satisfactory:
>
> [Sun Sep 01 17:32:32 2002] [notice] Apache/2.0.40 (Unix) mod_python/3.0.0-BETA Python/2.2.1 configured -- resuming normal operations
> [Sun Sep 01 17:32:39 2002] [notice] child pid 35323 exit signal Segmentation fault (11)
> [Sun Sep 01 17:32:39 2002] [notice] child pid 35324 exit signal Segmentation fault (11)
>
> All I did was put this line in httpd.conf:
> LoadModule python_module libexec/apache2/mod_python.so
>
> I didn't even call a Python handler, yet.
>
> Any clues?
>
> Gerhard
> --
> mail:   gerhard <at> bigfoot <dot> de       registered Linux user #64239
> web:    http://www.cs.fhm.edu/~ifw00065/    OpenPGP public key id AD24C930
> public key fingerprint: 3FCC 8700 3012 0A9E B0C9  3667 814B 9CAA AD24 C930
> reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://www.modpython.org/mailman/listinfo/mod_python
>