[ http://issues.apache.org/jira/browse/MODPYTHON-138?page=comments#action_12367799 ]
Graham Dumpleton commented on MODPYTHON-138: -------------------------------------------- Suggest this be put on hold anyway until original poster actually attaches here 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 because the same include is included twice with a different macro value." makes no sense. If header files are correctly protected with #ifndef they shouldn't be able to be included twice. Thus more information needed about the actual error message and which header files is supposedly being included twice, 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 is basically due to the fact that Python.h should be included first as > its defines some macros used by standard includes. When included at the end > of the includes, this results to some conflicts because the same include is > included twice with a different macro value. This change should have no > impact on platforms where the current include order works. > 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 > manage to find how to do it... > Michel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
