On 13 February 2011 06:55, commonzenpython <[email protected]> wrote: > i have successfully deployed django using mod_wsgi 3.3 and python 2.7 > turns out the apache/run directory didn't exist, however im not using > the shared libraries, because when i reinstalled python2.7 using the > shared libraries i could't even start the python interpreter i tried $ > python > and it would throw the following error : > error while loading shared libraries: libpython2.7.so.1.0: \ > cannot open shared object file: No such file or directory > > i tried editing the apache envvars file by adding : export > LD_LIBRARY_PATH = "/usr/local/lib:$LD_LIBRARY_PATH" > > but it still wouldn't work
When building mod_wsgi you should do: LD_RUN_PATH=/usr/local/lib make instead of just: make This will embed the library directory information in mod_wsgi.so so it knows where to pick up Python shared library from. If using an Apache supplied by Linux distribution, envvars file may not work as they change startup so it is ignored and so instead necessary to put it in init.d startup file for Apache instead. Thus, LD_RUN_PATH method better. 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.
