[mod_python] Installation Issues - Apache2 Python2.2 RedHat

Josh -

If you're using Apache 2, you need mod_python version 3.0, currently in
beta. Mod_python 2.7.8 won't work with apache 2.

But with respect to your specific question - rm config.cache and re-run
configure. (It will report the Python version correctly, but you're still
going to have the above-mentioned apache2 problem).

Grisha

On Mon, 11 Nov 2002, Joshua Gramlich wrote:

> Howdy.  I've looked through the archives and couldn't find anything in particularly specific to my issue, so here goes:
>
> I'm trying to install mod_python with thread support (no reason, just because).  I made the jump up to Apache2, and it is working fine.  I've also got Python 2.2.1 installed.  I'm using RedHat 7.2 as my platform, and python2 is installed via source RPM(./configure'd, make'd, and make install'd).  Apache, I compiled from source.
>
> When I configure mod python I do so like this:
>
> ./configure --with-apxs=/usr/local/apache/bin/apxs --with-python=/usr/src/redhat/SOURCES/Python-2.2.1
>
> ...and I get the following (partial):
>
> hecking for Apache include directory... -I/usr/local/httpd-2.0.43/include
> checking for --with-apache... no
> configure: warning: **** No apache sources specified, static compilation will not be available.
> configure: warning: **** You can use --with-apache to specify where your Apache sources are.
> checking for --with-python... /usr/src/redhat/SOURCES/Python-2.2.1
> checking for python... (cached) /usr/bin/python
> checking Python version... 1.5
> checking whether Python is compiled with thread support... yes
>
>   ****** WARNING ******
>   Python is compiled with thread support. Apache 1.3 does not use threads.
>   On some systems this will cause problems during compilation, on others
>   it may result in unpredictable behaviour of your Apache server. Yet on
>   others it will work just fine. The recommended approach is to compile
>   Python without thread support in a separate location and specify it with
>   --with-python option to this ./configure script.
>
> checking Python install prefix... /usr
> checking what libraries Python was linked with... grep: /usr/src/redhat/SOURCES/Python-2.2.1/Modules/Makefile: No such file or directory
> grep: /usr/src/redhat/SOURCES/Python-2.2.1/Modules/Makefile: No such file or directory
> /usr/src/redhat/SOURCES/Python-2.2.1/libpython1.5.a
> checking linker flags used to link Python...  -Xlinker -export-dynamic
>
>
>
> ...So anyways, I keep seeing "checking Python version...1.5" and I'm wondering if this is a problem.  Reason being, when I type "make dso" after configuring mod_python, I get this:
>
> make dso
> make[1]: Entering directory `/usr/src/mod_python-2.7.8/src'
> gcc  -I/usr/src/mod_python-2.7.8/src/include -I/usr/local/httpd-2.0.43/include -I/usr/src/redhat/SOURCES/Python-2.2.1 -I/usr/src/redhat/SOURCES/Python-2.2.1/Include    -c -o mod_python.o mod_python.c
> In file included from mod_python.c:54:
> /usr/src/mod_python-2.7.8/src/include/mod_python.h:93: parse error before `*'
> /usr/src/mod_python-2.7.8/src/include/mod_python.h:93: warning: data definition has no type or storage class
> /usr/src/mod_python-2.7.8/src/include/mod_python.h:96: parse error before `python_module'
> /usr/src/mod_python-2.7.8/src/include/mod_python.h:96: warning: data definition has no type or storage class
> In file included from /usr/src/mod_python-2.7.8/src/include/mod_python.h:99,
>                  from mod_python.c:54:
> /usr/src/mod_python-2.7.8/src/include/util.h:57: parse error before `*'
> In file included from /usr/src/mod_python-2.7.8/src/include/mod_python.h:100,
>                  from mod_python.c:54:
> /usr/src/mod_python-2.7.8/src/include/tableobject.h:69blablahblahblah....
>
>
>
> Anyone have any ideas as to why this isn't working?
>
>
> Josh
> Chicago, IL