[ http://issues.apache.org/jira/brows...236
7799 ]

Graham Dumpleton commented on MODPYTHON-138:
--------------------------------------------

Suggest this be put on hold anyway until original poster actually attaches h
ere the original output from the build, including compiler options and error
 output.

I suggest this, as their original comment:

"When included at the end of the includes, this results to some conflicts be
cause the same include is included twice with a different macro value."

makes no sense. If header files are correctly protected with #ifndef they sh
ouldn't be able to be included twice. Thus more information needed about the
 actual error message and which header files is supposedly being included tw
ice, so it can be debugged
properly rather than trying to solve it by just shifting stuff around.

> Python.h should be included first
> ---------------------------------
>
>          Key: MODPYTHON-138
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-138
>      Project: mod_python
>         Type: Bug
>   Components: core
>     Versions: 3.2
>  Environment: Tru64 5.1B, Python 2.4.1, Apache 2..55
>     Reporter: Michel Jouvin
>     Assignee: Jim Gallacher
>  Attachments: mod_python-3.2.6-tru64.patch
>
> I have a problem to build mod_pyton on Tru64 with the Python config I have. This i
s basically due to the fact that Python.h should be included first as its defines so
me macros used by standard includes. When included at the end of the includes, this 
res
ults to some conflicts because the same include is included twice with a different macro val
ue. This change should have no impact on platforms where the current include order works.[vb
col=seagreen]
> Affected files are :
>       src/include/psp_parser.h
>       src/include/mod_python.h
>       src/include/psp_flex.h
>       src/include/mod_python.h.in
>       src/_pspmodule.c
>       src/psp_parser.c
> I have a patch file available, I'll try to attach it to this issue if I ma
nage to find how to do it...
> Michel[/vbcol]

[ Post a follow-up to this message ]