Thanks, I will look at your workarounds. On my system the troubles seem to be because /usr/lib64 gets put into RPATH in all the .so libs in subversion/bindings/swig/python/* (including the subdirectories). It is put in RPATH before the path element for the apr, apr-util that I have built. If I use patchelf to reset the RPATH removing /usr/lib64 entirely in subversion/bindings/swig/python/.libs/_core.so then all the checks pass. Note that I removed /usr/lib64, I didn't move it to the end of the RPATH. So now I ask why does /usr/lib64 get put into the RPATH at all? It seems to cause a lot of problems, and not only with the bindings.
On Fri, Jul 29, 2011 at 10:32 AM, Stefan Sperling <s...@elego.de> wrote: > On Fri, Jul 29, 2011 at 09:12:57AM -0600, tsteven four wrote: > > ldd and readelf shown above. Is there some method to get python use the > > RPATH in libsvn_ra_serf as ldd does so the correct libapr is found, or is > > the python check overriding RPATH with > > some method like LD_LIBRARY_PATH? > > Yes, you need to set LD_LIBRARY_PATH. > You also need to make sure that none of the libraries that get loaded > indirectly load the incompatible system libraries... it can get quite > hairy. > See this for various workarounds that I use in my build: > https://svn.apache.org/repos/asf/subversion/trunk/tools/dev/unix-build/ >
