Comments on: The quest for MacOSX 10.5, Apache, Python, Django, and mod_wsgi

By: Dave Everitt

Dave Everitt — Wed, 18 Aug 2010 13:51:06 +0000

I looked into this and decided (like you) for now to thin Apache in the ‘reversible’ manner suggested, which works under my 32 bit Python 2.6 and OS X 10.5 Intel system:

http://groups.google.com/group/modwsgi/browse_thread/thread/cacddadc0c3c8e93

However, the Python 2.7 OS X installer is now ‘full fat’ (unlike the 32 bit 2.6 version), so – as Graham suggests – I could restore the 64 bit Apache and try again with everything full fat. Although, the 32/64 bit architecture issue first surfaced when I used easy_install for MySQL-Python, so I’d have to re-install that too, but (at time of writing) it is only officially supported up to Python 2.6.

Then there’s the re-install and configure MySQL as 64 bit, and time soon runs out, when all I really wanted to do (oh, about 3 months ago) was to get that little Django blog app working locally under mod_wsgi before deploying… well, at least I can now do that. The rest will have to wait for another slack weekend or so…

By: Andy

Andy — Fri, 02 Oct 2009 22:57:52 +0000

Hey Graham, thanks for your comment! I’m fairly new to Apache, modules, and dealing with 64-bit on Mac, among other things, so this was a good learning experience. I did read through that wiki for wsgi on MacOSX, and the problem was not with mod_wsgi.so. I verified that the Makefile was building mod_wsgi with the full “fat” set of architectures. I believe the problem I was seeing was that the Python library was only built in 32-bit mode. I figured the solution to this problem would be to either try to build the Python library with all archs, or thin Apache down to 32-bits. I was hoping to not have to thin Apache down, but that seems to be the easiest solution. What are your thoughts?

By: Graham Dumpleton

Graham Dumpleton — Fri, 02 Oct 2009 09:58:34 +0000

Rather than search through all those blogs, you could have just read:

http://code.google.com/p/modwsgi/wiki/InstallationOnMacOSX

It mentions how to build fully fat framework from source code as well as mention tricks for thinning Apache etc if absolutely needed.

The particular error you are getting also possibly not entirely related to that anyway and may be because wrong version of Python framework being picked up at run time. You need to check with ‘otool’ what mod_wsgi.so thinks it will find. If it isn’t right, you need to change how mod_wsgi is linked against Python framework.

Easiest thing to do is make sure using mod_wsgi 2.6 and if standard configure doesn’t work, use the ‘–disable-framework’ option to configure to force linking via old style library reference. Don’t know why but different Python installations and operating system versions appear not to be consistent as to what works.