By the way libpython2.7.so.1.0 definitely does now exist in my virtual environment and is readable (I'm building mod_wsgi with sudo).
On Friday, 10 August 2012 14:32:44 UTC+10, quantoid wrote: > > Thanks for responding. I tried to rebuild against my new 2.7.3 > installation but failed with "libpython2.7.a: could not read symbols: Bad > value", which you've already pointed out elsewhere is because python has to > be built with --enable-shared. I tried to rebuild python with that option > but I get the same error there, which is because the makefile links against > any existing python2.7 libraries in preference to the one it's rebuilding! > > http://www.gossamer-threads.com/lists/python/python/862272 > > I temporarily renamed the existing libraries so that it links against the > new one and was able to rebuild python 2.7 but now I get this error when > building mod_wsgi: > > /usr/lib/mypy/bin/python: error while loading shared libraries: > libpython2.7.so.1.0: cannot open shared object file: No such file or > directory > > Is it looking for the python library in PREFIX/lib rather than my virtual > environment? Specifying a different PREFIX probably won't work because it's > only python that's not in a standard location. > > What would be a good place to put a virtual environment, given the access > restrictions on home directories effectively rule those out? I used > /usr/lib because someone else had already installed python2.6 and a bunch > of other things there. > > What a chain-of-pain this has been! Thanks for your help though. > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To view this discussion on the web visit https://groups.google.com/d/msg/modwsgi/-/VHXmDMH9IAsJ. 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.
