Antonio Rodriguez
Antonio at Memora.com
Mon Jun 21 19:14:50 EDT 2004
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
|