[mod_python] Re: mod_python on leopard

Graham Dumpleton graham.dumpleton at gmail.com
Sat Jan 5 23:58:57 EST 2008


Get rid of the space in the directory name where you have the
mod_python source code. ie., 'python stuff'.

Graham

On 06/01/2008, Bob Pasker <bob at pasker.net> wrote:
> It looks like these are fat binary and 64-bit intel problems.
>
> Im building for ppc and a skinny ppc binary will work fine.
>
> --bob
>
> ---------
> Sent from my mobile
>
> On Jan 5, 2008, at 19:51, "Graham Dumpleton"
> <graham.dumpleton at gmail.com> wrote:
>
> > On 06/01/2008, Bob Pasker <bob at pasker.net> wrote:
> >> Hi Justin and Graham -- i just updated the mod_python bug you guys
> >> reported about building mod_python on OS X. I was wondering if you
> >> had
> >> found a workaround. thanks, bob
> >>
> >> http://issues.apache.org/jira/browse/MODPYTHON-186
> >
> > That issue isn't quite the same as current MacOS X Leopard issues.
> > There seemed to be a specific problem with one version of gcc/XCode
> > provided by Apple not coping with the potentially bogus command line
> > options being passed it.
> >
> > The Leopard problem is that the -arch flags aren't being passed to the
> > compiler so as to create a fat object file. The default of creating a
> > i386 object is not sufficient as Apache on Leopard runs as x86_64.
> >
> > You will find this issue discussed in mod_python mailing list
> > archives. There are a couple of parts to it. The first is the building
> > of the Apache module, the second is the building of the psp support
> > module for Python. See both:
> >
> >  http://www.modpython.org/pipermail/mod_python/2007-October/
> > 024394.html
> >  http://www.modpython.org/pipermail/mod_python/2008-January/
> > 024635.html
> >
> > If you can't follow through these discussions and get it working and
> > only need WSGI hosting ability, maybe look at mod_wsgi 2.0 which
> > already builds out of the box for Leopard.
> >
> > Graham
> >
>


More information about the Mod_python mailing list