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
checking Apache version... 2.2.22
configure: creating ./config.status
config.status: creating Makefile
<hostname>:mod_wsgi-3.4 <user>$ make
make: Nothing to be done for `all'.
<hostname>:mod_wsgi-3.4 <user>$ sudo make install
Password:
/usr/sbin/apxs -i -S LIBEXECDIR=/usr/libexec/apache2 -n 'mod_wsgi'
mod_wsgi.la
/usr/share/httpd/build/instdso.sh
SH_LIBTOOL='/usr/share/apr-1/build-1/libtool' mod_wsgi.la
/usr/libexec/apache2
/usr/share/apr-1/build-1/libtool --mode=install cp mod_wsgi.la
/usr/libexec/apache2/
cp .libs/mod_wsgi.so /usr/libexec/apache2/mod_wsgi.so
cp .libs/mod_wsgi.lai /usr/libexec/apache2/mod_wsgi.la
cp .libs/mod_wsgi.a /usr/libexec/apache2/mod_wsgi.a
chmod 644 /usr/libexec/apache2/mod_wsgi.a
ranlib /usr/libexec/apache2/mod_wsgi.a
----------------------------------------------------------------------
Libraries have been installed in:
/usr/libexec/apache2
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `DYLD_LIBRARY_PATH' environment variable
during execution
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
chmod 755 /usr/libexec/apache2/mod_wsgi.so
When I run otool I still get the same output,
<hostname>:apache2 <user>$ otool -L mod_wsgi.so
mod_wsgi.so:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
169.3.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
(compatibility version 150.0.0, current version 744.12.0)
The version of mod_wsgi is the tar that is available at the following
location download
here<http://code.google.com/p/modwsgi/downloads/detail?name=mod_wsgi-3.4.tar.gz&can=2&q=>
.
Any ideas?
Thanks
Jake
On Wednesday, October 3, 2012 12:02:16 AM UTC+1, Jake wrote:
>
> Hi
>
> Until recently I have developing in python using mod_python but decided to
> upgrade to mod_wsgi when I upgraded from os snow leopard to mountain lion.
>
> I have followed the instructions and when I restart apache it fails to
> start up. To throw things into the mix I am trying to run mod_wsgi on
> python 3.2. I think that this should work.
>
> If I run the command
>
> "otool -L mod_wsgi.so"
>
> I get ...
>
> mod_wsgi.so:
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
> 169.3.0)
> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
> (compatibility version 150.0.0, current version 744.12.0)
>
> From what I can see from the notes that have been pasted this is not
> correct.
>
> Can anyone point me in the right direction, an idiot guide would be useful.
>
> Thanks
>
> J
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/modwsgi/-/JvTfxYObF74J.
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.
