Antonio Rodriguez
Antonio at Memora.com
Tue Jun 22 19:25:23 EDT 2004
Justin, Good idea. I'd be happy to start a wiki on mod_python/OSX integration, or if a wiki already exists, to start a wiki page. If someone knows of an appropriate wiki, please just let me know where to start posting. If I don't hear from anyone, I'm happy to start it/ host it. > I haven't tried using this new python to build mod_python 2.7 against > apache 1.3 from panther because I'd rather use apache2. I'd rather > run it out of daemontools anyway. I take it in the end you got it to work? Only on apache2? Also, am I to assume that mod_python 3 is all that anyone cares about? That is, is mod_python like subversion, another reason for all of us to go to apache2? AR On Jun 22, 2004, at 5:06 PM, Justin Ryan wrote: > Antonio, > > I feel your pain. I spent about 3 weeks trying to get mod_python > working on my new powerbook. I first tried (much like yourself) to > build against apache and python2.3 from panther, but got errors trying > to link against libpython2.3.a (which did not exist on my system). > > I tried installing python about every way possible for OSX. moved > apple's python aside and installed MacPython. Installed python from > fink and darwinports. From source into /usr/local. Eventually, I > decided that not using apple's python was causing more grief than it > was helping, so I decided to rebuild and install over the original > python (I tarred up /Library/Frameworks/Python.Framework - and I > suggest you do the same ;p). > > So, although I would really have rather not, I built apple's python > from source (in fact, I upgraded to 2.3.4). just ./configure > --prefix=/usr --enable-framework --enable-shared --enable-threads. > > I'm not 100% sure if everything is in place on panther to build python > exactly as apple did (with all of the pyobjc stuff linked to cocoa and > whatnot). i don't use that stuff, so I haven't tested it, but there > is a ton of documentation in the Mac/OSX directory of the python > source tree. > > I haven't tried using this new python to build mod_python 2.7 against > apache 1.3 from panther because I'd rather use apache2. I'd rather > run it out of daemontools anyway. > > I noticed that there are a few of us with a mix of success/failure > running mod_python on osx. perhaps we should compile a howto and/or > start a wiki. > > Cheers! > > -=JR > > On Jun 21, 2004, at 5:14 PM, Antonio Rodriguez wrote: > >> Hello all, >> >> I'm trying to build mod_python for OSX for development. I've used it >> in production on linux and its been great. But since all of us at >> work have gotten groovy Apple laptops, I wanted to re-create our >> environment. >> >> So, build environment: >> >>> * Stock OSX 10.3 (Panther) >>> * Apache/1.3.29 (Darwin) (stock build) >>> * mod_python/2.7.10 Python/2.3 (using stock Apple python) >> >> For the build I wanted to use the Apple python even though its built >> with threads (on linux I've had no issues with mod_python with a >> threaded python so long as I dont run threaded code) because its >> what's there. The good news is that the configure test for threads on >> 2.3 fails so no warning is issued. >> >> That said, I had to make two changes to the src/Makefile. First I had >> to add -DEAPI to the gcc options (which I've had to do on linux for a >> while, why don't we make this part of the standard build file?). >> Then-- and here is the questionable part-- I had to change the >> include for the python static library (libpython2.3.a) to point to: >> >>> LIBS=-lm /System/Library/Frameworks/Python.framework/Python -ldl >> >> from: >> >>> /System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >>> python2.3/config/libpython2.3.a -ldl >> >> which was what configure chose. >> >> I think this is the right thing to do as Apple has a sort of weird >> default python. >> >> That said, when I try to run the test example from the docs, I get >> this in the apache error log: >> >>> [Mon Jun 21 17:50:21 2004] [notice] child pid 3206 exit signal Bus >>> error (10) >> >> Which I presume means that the apache child is seg-faulting for some >> reason. >> >> Now, here is my question: is anyone out there using mod_python in >> this configuration on OSX? I know that we should be using apache2 but >> OSX (as well as Debian my production environment) is running way >> behind the ball on apache2 so I'm trying to build for 1.3. If anyone >> can point me in the right direction, I'm glad to take on the task of >> trying to build a package for OSX that people can use without having >> to go through the build process. >> >> Thanks, >> >> Antonio >> >> _______________________________________________ >> Mod_python mailing list >> Mod_python at modpython.org >> http://mailman.modpython.org/mailman/listinfo/mod_python >> > >
|