Dear Graham

Thank you for taking the time to try to help me.  In order to make
this most efficient, I pasted as much information about my environment
into the original post as I thought was needed.  I followed the
instructions in the Wiki as close as possible and arrived at an
executable that would compile and could be loaded by Apache.
>
> Why did you edit the generated Makefile? There should have been no
> need for you to be making those changes. Please try without doing that
> and post the specific problem you were trying to address that may have
> occurred before that.

The problem was that the Makefile included instructions for 32 and 64
bit versions of Intel and PPC architectures, and would not compile.
The error I encountered was:

/usr/local/python-2.5.4/frameworks/Python.framework/Versions/2.5/
include/python2.5/pyport.h:761:2: error: #error "LONG_BIT definition
appears wrong for platform (bad gcc/glibc config?)."


>
> On doing that, post the values of those flags from unmodified
> makefile,

here is the value of these lines in the original Makefile:

CPPFLAGS =  -I/usr/local/python-2.5.4/frameworks/Python.framework/
Versions/2.5/include/python2.5 -DNDEBUG
CFLAGS =  -Wc,'-arch ppc7400' -Wc,'-arch ppc64' -Wc,'-arch i386' -Wc,'-
arch x86_64'
LDFLAGS =   -L/usr/local/python-2.5.4/frameworks/Python.framework/
Versions/2.5/lib/python2.5/config  -arch ppc7400 -arch ppc64 -arch
i386 -arch x86_64

for succesful compilation, I removed everything except -arch i386 to
get a 32 bit executable for Intel.


plus 'ls -las' of the directory:
>
>   
> /usr/local/python-2.5.4/frameworks/Python.framework/Versions/2.5/lib/python2.5/config

here is the ls -las output.

0 drwxr-xr-x   12 root  wheel    408 May 20 16:39 .
 0 drwxr-xr-x  598 root  wheel  20332 May 20 16:39 ..
80 -rw-r--r--    1 root  wheel  39767 May 20 16:39 Makefile
40 -rw-r--r--@   1 root  wheel  17862 May 20 16:39 Setup
 8 -rw-r--r--    1 root  wheel    368 May 20 16:39 Setup.config
 8 -rw-r--r--    1 root  wheel     41 May 20 16:39 Setup.local
 8 -rw-r--r--    1 root  wheel   2066 May 20 16:39 config.c
 8 -rw-r--r--@   1 root  wheel   1446 May 20 16:39 config.c.in
16 -rwxr-xr-x@   1 root  wheel   7122 May 20 16:39 install-sh
 8 lrwxr-xr-x    1 root  wheel     15 May 20 16:39 libpython2.5.a -
> ../../../Python
16 -rwxr-xr-x@   1 root  wheel   7431 May 20 16:39 makesetup
24 -rw-r--r--    1 root  wheel  11392 May 20 16:39 python.o


>
> And the after a make, the output of running:
>
>   otool -L .libs/mod_wsgi.so

ch...@chw-air:/tmp/mod_wsgi-2.5 % otool -L .libs/mod_wsgi.so
.libs/mod_wsgi.so:
        /System/Library/Frameworks/Python.framework/Versions/2.5/Python
(compatibility version 2.5.0, current version 2.5.1)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.1.3)
        /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)

I see here that it links to the python framework of the OS, but I have
no idea why.


I have tried everything else I could think of, including setting this
line in httpd.conf:

WSGIPythonHome /usr/local/python-2.5.4/

and setting this environment variable in the apache environment:

PYTHONEXECUTABLE=/usr/local/python-2.5.4/bin/python

and even modified the link to python in /usr/bin to point to

/usr/local/python-2.5.4/bin/python instead of the system provided
python.  However nothing of all this prevented mod_wsgi from running
with Pyghon 2.5.1 instead of my 2.5.4.

Is there anything else I could do or try?


Chris
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to