jvandal / modwsgi

Automatically exported from code.google.com/p/modwsgi
0 stars 0 forks source link

Not finding Python shared library when building mod_wsgi. #118

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Sorry about taking this route, but I couldn't figure out how to edit the
wiki page!

Configuring Apache/Python for SLED 10.2 I came across the problems noted in
InstallationIssues - "If rebuilding Python to generate a shared library, do
make sure that the Python shared library, or a symlink to it appears in the
Python 'config' directory of your Python installation.....".

I found recompiling Pyton2.5 with LD_RUN_PATH set at build time to include
/usr/local/lib solved this exact same problem for me. 

An alternative I did not try may be to set LD_LIBRARY_PATH at run time to
include /usr/local/lib.

Original issue reported on code.google.com by wasserfu...@gmail.com on 14 Dec 2008 at 9:20

GoogleCodeExporter commented 8 years ago
this meant I didn't need the "ln -s .." option you mention (which didn't seem 
to work
in my setup)

Original comment by wasserfu...@gmail.com on 14 Dec 2008 at 9:22

GoogleCodeExporter commented 8 years ago
Neither of those should change whether mod_wsgi linked to the shared library or 
not at compile time. If the .so 
file for Python library is not in same directory next to the .a, then linker 
will use the .a instead. The linker will 
not use .so if it is in a different directory mentioned later in library search 
path. So, the symlink needs to be 
there. If not, mod_wsgi will be compiled with static .a combined into it. You 
should double check by running 'ldd' 
on mod_wsgi.so file to see if it is linking against Python .so or not.

Original comment by Graham.Dumpleton@gmail.com on 15 Dec 2008 at 4:03

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Not believed to be a mod_wsgi documentation or mod_wsgi code issue. Steps 
perhaps not followed correctly.

Do perhaps need to consider again the 'configure' script for mod_wsgi adding in 
parent directory two levels up 
from Python config directory if it can confirm shared library likely to be 
there. Deal with that enhancement as 
separate issue.

Original comment by Graham.Dumpleton@gmail.com on 6 Feb 2009 at 7:49