2010/1/12 sborf <[email protected]>: > I cross compiled apache and mod_wsgi for an arm machine and now "$./ > apachectl start" runs fine. > When I request a page I see in errors.log an ImportError for every > module I could ask for both so and sys and any other module in site- > packages if I exec the python interpreter in a shell I could import > every module without the ImportError. I was wondering if I missed the > site-packages path inside some configure file?
If you cannot even import 'sys' module you have a big problem, as that is a compiled in module in Python and so any issue with module search path can't affect ability to import it. To comment further I really need to see the exact messages from the Apache error log. One thing though to perhaps try, is to use the WSGIPythonHome directive to specify the home directory for the Python installation in case it isn't being derived correctly. To work out what to set it to, run command line Python and dump out sys.prefix. For example: $ python Python 2.6.1 (r261:67515, Jul 7 2009, 23:51:51) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.prefix '/System/Library/Frameworks/Python.framework/Versions/2.6' Thus for that case would use: WSGIPythonHome /System/Library/Frameworks/Python.framework/Versions/2.6 This directive must be used at global scope in Apache configuration outside of all VirtualHost directives etc. For anyone else reading this, using WSGIPythonHome is the exception, not the norm, so just because suggesting this, don't think you have to use it as part of normal practice. Anyway, send those error messages and can then suggest other things. 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.
