Hi Michel,

Please create a JIRA issue. We are much less likely to loose track of it if it's in the issue tracker.

Thanks,
Jim


Michel Jouvin wrote:
0  Tru64 5.1B-3, Apache 2.0.55, worker MPM, Python 2.4.1

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.

I reported this a couple of months ago during 3.2 beta. Do you want me to resubmit this problem via JIRA ? Or just to resend the required fixes ?

Cheers,

Michel

--On lundi 20 février 2006 16:18 -0500 Graham Dumpleton <[EMAIL PROTECTED]> wrote:

+1 core vote

Nicolas Lehuen wrote ..

+1 core vote

2006/2/20, Jim Gallacher <[EMAIL PROTECTED]>:
> +1 core vote
>
> Jim
>
> Gregory (Grisha) Trubetskoy wrote:
> >
> > Based on summary below, +1 from for putting it out there.
> >
> > Grisha
> >
> >
> > Graham Dumpleton <[EMAIL PROTECTED]>
> > +1 Mac OS X 10.4, apache 2.0.55 mpm-worker, python 2.3.5 (3.2.x SVN
> > trunk)
> >
> > Nicolas Lehuen <[EMAIL PROTECTED]>
> >   +1 mod_python 3.2.8 + Apache/2.0.55 + Python/2.2.3 + Windows 2000
SP4
> >   +1 mod_python 3.2.8 + Apache/2.0.55 + ActivePython/2.3.5 + Windows
> > 2000 SP4
> >   +1 mod_python 3.2.8 + Apache/2.0.55 + ActivePython/2.4.2 + Windows
XP SP2
> >
> > Barry Pederson <[EMAIL PROTECTED]>
> >   +1 FreeBSD 6.0, apache 2.0.55 mpm-prefork, python 2.4.2
> >
> > Jim Gallacher <[EMAIL PROTECTED]>
> >   +1 Debian sid, apache 2.0.55 mpm-prefork, python 2.3.5
> >
> >
>
>




    *************************************************************
    * Michel Jouvin                 Email : [EMAIL PROTECTED] *
    * LAL / CNRS                    Tel : +33 1 64468932        *
    * B.P. 34                       Fax : +33 1 69079404        *
    * 91898 Orsay Cedex                                         *
    * France                                                    *
    *************************************************************




Reply via email to