| Michel Jouvin 2005-12-19, 5:47 pm |
| Hi,
I managed to find some time and rebuild mod_python after fixing the problem =
of macro conflict between standard includes included by mod_python and the=20
same includes included by Python.h.
The problem is that Python.h defines a few macros used by standard includes =
to non standard values (if I remember correctly this comes from BerkelyDB=20
includes). Thus it is important to have these macros defined before=20
including any standard .h. An easy workaround is to always include Python.h =
before any other include. The files that need to be modified are :
../src/include/mod_python.h
../src/include/psp_parser.h
../src/_pspmodule.c
../src/psp_parser.c
../src/mod_python.c
May be this could be included in the standard distribution (I can provide=20
diff files but this is so easy to do..).
This doesn't solve the issue with starting a new child. I'll try to put=20
some additional logging messages in mod_python.c
Michel
--On samedi 10 d=C3=A9cembre 2005 09:37 +0100 Michel Jouvin=20
<jouvin@lal.in2p3.fr> wrote:
> Graham,
>
> No I am not using any PythonImport directive neither on the prod server,
> nor on the test server. On the test server, the only mod_python related
> directive is :
>
> LoadModule python_module modules/mod_python.so
>
> I'll try you suggestion about adding some logging messages in
> mod_python.c. By the way, I just remember that I had one problem to build
> mod_python on Tru64 with the native compiler (not tried with gcc) because
> of definition conflict for macro _XOPEN_SOURCES defined by Phyton
> pyconfig.h. The problem is that mod_python includes types.h without this
> macro defined to the value used by Python and before including pyconfig.h
> (Python.h). My hack was pretty dirty : undefine this macro in pyconfig.h
> to build mod_python successfully. But may be it is responsible for this
> side effect (unfortunatly this seems the only one...).
>
> I'll try to find the time to check this in the coming days...
>
> Michel
>
> --On samedi 10 d=C3=A9cembre 2005 15:00 +1100 Graham Dumpleton
> <grahamd@dscpl.com.au> wrote:
>
>
>
>
> ****************************************
*********************
> * Michel Jouvin Email : jouvin@lal.in2p3.fr *
> * LAL / CNRS Tel : +33 1 64468932 *
> * B.P. 34 Fax : +33 1 69079404 *
> * 91898 Orsay Cedex *
> * France *
> ****************************************
*********************
>
****************************************
*********************
* Michel Jouvin Email : jouvin@lal.in2p3.fr *
* LAL / CNRS Tel : +33 1 64468932 *
* B.P. 34 Fax : +33 1 69079404 *
* 91898 Orsay Cedex *
* France *
****************************************
*********************
|