Hi Graham, many thanks for your prompt help! :-)
Am Dienstag, 6. Mai 2014 01:17:54 UTC+2 schrieb Graham Dumpleton: > > On 06/05/2014, at 8:25 AM, Carsten Fuchs <[email protected] <javascript:>> > wrote: > > These steps were also necessary: > > $ cd /usr/local/lib/python2.7/config/ > $ sudo ln -s ../../libpython2.7.so . > > This shouldn't be necessary, the link line uses: > > -L/usr/local/lib -L/usr/local/lib/python2.7/config > > and so it looks in both locations anyway. > Ok, thanks for pointing this out. I created the symlink because after running `make`, I couldn't find the mod_wsgi.py. Then I suspected that something was silently failing (wrongly, as you described below), and as creating the symlink was suggested at http://code.google.com/p/modwsgi/wiki/InstallationIssues#Lack_Of_Python_Shared_Library, it looked like a good idea. ;-) > & cd /usr/local/bin/ > $ sudo ldconfig # or else we cannot call the python2.7 binary > > More likely you should have set LD_RUN_PATH when compiling mod_wsgi. [...] > > If the issue was that 'python' itself wasn't running because it couldn't > find the shared library, then that is distinct from mod_wsgi, but you could > have used the same LD_RUN_PATH workaround when building Python itself. > Yes, I (re-)built Python with --enable-shared, then found that it itself way no longer working. I was aware that this is unrelated to mod_wsgi, but didn't know that LD_RUN_PATH could have been used, so I used `ldconfig` to fix the problem. > The true output of the build is in the .libs sub directory. > > Running 'make install' would have grabbed the mod_wsgi.so from the .libs > sub directory. > Wow, I think that this was the source of all my problems: I didn't know and didn't realize that the output was put into the hidden .libs directory, and after the `make` step, in an attempt of being cautious, it was the apparent lack of the result that caused me to create the symlink and eventually to post here. I just checked again, the file is there, `ldd` output with and without LD_LIBRARY_PATH looks good, and I think that I can now proceed and configure apache to use it. :-) My best thanks! Best regards, Carsten -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
