Hi Graham
I have carried out the make install now and when I run the otool on the
installed mod_wsgi.so I get the following result;
mod_wsgi.so:
/Library/Frameworks/Python.framework/Versions/3.2/Python (compatibility
version 3.2.0, current version 3.2.0)
/usr/lib/libSystem.B.dylib
With Mountain lion it comes with versions 2.3, 2.5, 2.6, 2.7. These are
installed as you have correctly stated however the installation is a little
different compared to a linux installation.
The version 3.2 that I have installed is from the python site at the
following location
With otool -L showing the correct result, what then was the result
when you tried to actually use it with Apache???
If there is still a run time linking issue causing Apache not to
start, you can usually see the error by running:
sudo /usr/sbin/apachectl -t
It will show any linker error as
Graham
These are the steps that I followed and the output I received;
1.
./configure
--with-python=/Library/Frameworks/Python.framework/Versions/3.2/bin/python3
--disable-framework
2.
make
3.
cd .libs
4.
otool -L mod_wsgi.so
Output
mod_wsgi.so:
The output is correct, although one thing worried me.
Can you confirm that you manually installed Python 3.2, because a
system Python wouldn't be under:
/Library/Frameworks/Python.framework
What Python versions are under:
/System/Library/Frameworks/Python.framework/Versions
I ask as I am
Hi Graham, thanks for the pointer but it hasn't worked. Here is what I
entere into terminal;
hostname:mod_wsgi-3.4 user$ ./configure
--with-python=/Library/Frameworks/Python.framework/Versions/3.2/bin/python3
--disable-framework
checking for apxs2... no
checking for apxs... /usr/sbin/apxs
Run 'make distclean' in the directory before you rerun configure. You
still had old build results lying around by the look of it.
On 4 October 2012 05:08, Jake jake.griff...@realspaces.com wrote:
Hi Graham, thanks for the pointer but it hasn't worked. Here is what I
entere into terminal;
I had deleted the previous download and started with a clean one. Not sure
if the 'make distclean' will do anything.
I ran it anyway and got the following ;
make: *** No rule to make target `distclean'. Stop.
Which I think is to be expected.
On Wednesday, October 3, 2012 12:02:16 AM UTC+1,
The output you gave showed:
hostname:mod_wsgi-3.4 user$ make
make: Nothing to be done for `all'.
which indicated that make had already been run in the directory again.
From that fresh source code, do the configure and make and then run:
otool -L .libs/mod_wsgi.so
without doing an install.
