On 5 February 2010 07:08, Joe Hughes <[email protected]> wrote: > Hi Graham, > > I was assigned a Mac Mini Server to do the development on so let me > see if I can answer all your questions. Here is the sequence > > 1. Downloaded latest Development Tools from Apple
Why not just use the version of Apache supplied with the operating system? > 2. Downloaded latest Python source from Python.org Why not just use the version of Python supplied with the operating system? > 3. Tried to configure but found an issue What issue? Show the exact output and error messages you were presented with. > 4. Modified configure so it didn't have ppc64 as an architecture in the all > option > 5. Configured with no errors > > ./configure --prefix=/usr/local/python-3.1.1 \ > --enable-framework=/usr/local/python3.1.1/frameworks \ > --enable-universalsdk=/ MACOSX_DEPLOYMENT_TARGET=10.6 \ > --with-universal-archs=all This is wrong, as documented in: http://code.google.com/p/modwsgi/wiki/InstallationOnMacOSX on Snow Leopard you should have used: ./configure --prefix=/usr/local/python-3.1.1 \ --enable-framework=/usr/local/python3.1.1/frameworks \ --enable-universalsdk=/ MACOSX_DEPLOYMENT_TARGET=10.6 \ --with-universal-archs=3-way Note how '3-way' is used instead of 'all'. If you had done the right thing, you probably wouldn't have needed to hack Python configure script. > 6. Make with no errors > 7. Make install with no errors > 8. Linked python3.1.1 binary to /usr/local/bin/python3 > 9. Downloaded latest mod_wsgi > 10. Configured with no errors > > ./configure --with-python=/usr/local/bin/python3 > > 11. Make with no errors > 12. Make install with no errors > 13. Added > > LoadModule wsgi_module libexec/apache2/mod_wsgi.so > > to httpd.conf > 14. Checked apachectl -t and no errors > 15. Stopped and then started Apache > 16. Loaded the files onto the mac server > 17. Used the wrong URL which gave me an error with Apache/2.2.13 (Unix) > mod_wsgi/3.1 Python/3.1.1 > which tells me that mod_wsgi is working > 18. Got the right URL and got what I was expecting > > Thus except for the python configure bug (The Mac Mini reports ppc, i386, and > x86_64 for httpd) everything looks good. So, I take it that it is now working okay and you didn't actually investigate the reason for the original problem? That is, run 'apachectl -t' for original failing installation so could see if was a runtime symbol lookup problem as expected it may be based on limited information supplied. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
