Your scenario is slightly different to main one I believe I was complaining about previously. In your case, you don't have a Python installation in a location different to where Apple Python is installed.
The problem in your case, is that when different versions of Python are installed under same area and using -F/-framework options, you can only link to what is designated as the 'Current' version. I previously looked to see if there were command line options for designating alternate framework version from same area, but couldn't find one. The solution though is similar, to ignore the framework linking method and fallback to using -L/-l method. This works for Apple supplied Python, but doesn't work with some other distributions of Python, thus I could use -L/-l all the time. In other words, had to use -F/-framework as notionally that is the proper way of doing things, and when that doesn't work, require people to use -L/-l instead. You didn't need to modify the makefile to this though, you could have used the '--disable-framework' option to 'configure' when running it for mod_wsgi. I really need to update documentation as don't think it mentions this option. Graham On 8 August 2010 04:26, Phil Schumm <[email protected]> wrote: > On Sep 1, 2009, at 2:32 AM, Graham Dumpleton wrote: >> >> This is getting to be a pain in the neck. Some installations will not work >> when -F/-framework is used, showing the symptom you see instead, and require >> linking to libpython2.6.a to work. As far as I can tell it isn't related to >> the specific Python version but some other oddity which may even differ >> where people run same MacOS X version. :-( >> >> I'll have to yet more experimentation. Maybe I need to go back to >> -F/-framework if it is Snow Leopard. The current rule was if Python 2.3, >> 2.4 or 2.5 use -F/-framework and if later use -L/-l. > > > I don't know if this is relevant to your comments above, but I thought I'd > share our recent experience installing mod_wsgi 3.3 on OS X Server 10.6.4. > Although OS X 10.6 comes with Python 2.6.1, we have a few legacy > applications that we have not yet tested with 2.6, and so we wanted to > compile mod_wsgi against the Python 2.5 that also comes pre-installed on OS > X 10.6 (2.5.4). Thus, we used > > ./configure > --with-python=/System/Library/Frameworks/Python.framework/Versions/2.5/bin/python2.5 > > However, firing up Apache gives the following > > [Fri Aug 06 11:19:55 2010] [warn] mod_wsgi: Compiled for Python/2.5.4. > [Fri Aug 06 11:19:55 2010] [warn] mod_wsgi: Runtime using Python/2.6.1. > > To fix this, we changed the following two lines in our Makefile > > LDFLAGS = -Wl,-F/System/Library/Frameworks -framework Python -u > _PyMac_Error /System/Library/Frameworks/ -arch x86_64 -arch i386 -arch > ppc7400 > LDLIBS = -ldl > > to > > LDFLAGS = > -Wl,-L/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config > -arch x86_64 -arch i386 -arch ppc7400 > LDLIBS = -lpython2.5 -ldl > > IOW, our experience is exactly as you described above. Is it possible that > the differences you describe are related to the way in which Python is > installed (i.e., pre-installed versus self-compiled frameworks build)? > > > -- Phil > > -- > 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. > > -- 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.
