On 6 May 2011 11:19, Gnarlodious <[email protected]> wrote: > Hi, thanks for the help. I am running Apache version 2.2.17 > > I downloaded this file: mod_wsgi-3.3.tar.gz > otool says: > /usr/libexec/apache2/mod_wsgi.so: > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 125.2.10) > /System/Library/Frameworks/Python.framework/Versions/2.6/Python > (compatibility version 2.6.0, current version 2.6.1) > /System/Library/Frameworks/CoreFoundation.framework/Versions/A/ > CoreFoundation (compatibility version 150.0.0, current version > 550.42.0)
Which means it isn't finding Python 3.1 Python framework properly when doing runtime dynamic library resolution. > Which is a little odd because I built it with this config: > ./configure --with-python=/Library/Frameworks/Python.framework/ > Versions/3.1/bin/python3.1 Where did you get your Python installation from? Is this PSF installer, MacPorts, HomeBrew or your own installed version? Some Python installations (or it could be some specific MacOS X versions, still not sure) and broken and don't work properly when using framework linking mechanism. For those you have to use: ./configure --with-python=/Library/Frameworks/Python.framework/Versions/3.1/bin/python3.1 --disable-framework With the --disable-framework option it will use -L/-l to link Python library and > And no I am not running mod_python > > > So I deleted everything starting over: > > make > /usr/sbin/apxs -c -I/Library/Frameworks/Python.framework/Versions/3.1/ > include/python3.1 -DNDEBUG -Wc,'-arch x86_64' -Wc,'-arch i386' -Wc,'- > arch ppc7400' mod_wsgi.c -Wl,-F/Library/Frameworks -framework Python - > framework CoreFoundation -arch x86_64 -arch i386 -arch ppc7400 - > ldl The options ' -arch x86_64 -arch i386 -arch ppc7400' are used because that is the architectures that your Apache is compiled for. > /usr/share/apr-1/build-1/libtool --silent --mode=compile gcc - > DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -I/usr/local/include -I/usr/ > include/apache2 -I/usr/include/apr-1 -I/usr/include/apr-1 -arch > x86_64 -arch i386 -arch ppc7400 -I/Library/Frameworks/Python.framework/ > Versions/3.1/include/python3.1 -DNDEBUG -c -o mod_wsgi.lo mod_wsgi.c > && touch mod_wsgi.slo > /usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler (/usr/ > bin/../libexec/gcc/darwin/ppc/as or /usr/bin/../local/libexec/gcc/ > darwin/ppc/as) for architecture ppc not installed > Installed assemblers are: > /usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64 > /usr/bin/../libexec/gcc/darwin/i386/as for architecture i386 > lipo: can't open input file: /var/folders/cT/cTt6WEOMHLGOWZELu+r4nU++ > +TI/-Tmp-//ccKr9NKf.out (No such file or directory) > apxs:Error: Command failed with rc=65536 > . > make: *** [mod_wsgi.la] Error 1 > > What say about this error? What gcc version is this? Use 'gcc -v' to find out? Is that perhaps from the very latest XCode release? The compiler appears to not support ppc architecture. If you don't need ppc support, to avoid that problem you can modify the generated Makefile in mod_wsgi source code and remove "-Wc,'-arch ppc7400'" flag from CFLAGS and the '-arch ppc7400' flag from LDFLAGS. Then rerun the make. Also note that PSF Python installers have in the past not been fully fat. That is, they were only 32 bit and not 64 bit. Thus cannot be used under Apach which usually runs as 64 bit. There are workarounds which make Apache run 32 bit but usually people compile Python from source code themselves. Graham -- 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.
