On Mar 12, 9:51 am, Stefan Sperling <s...@elego.de> wrote: > Well,is libtool is constructing a linker command that which > contains -L /usr/lib64 which causes the linker to pick up svn > libraries that are already installed there.
It's most likely not libtool itself that's to blame here. May bet is on some misconfigured pkg-config (*.pc) file (or some old-style foo-config script) that leaks "-L /usr/lib64" into your build. > You should uninstall previously installed subversion libraries > before the build. Not very helpful. Probably better to set up a chroot environment for a clean build. The cost of setting one up would probably outweigh the pain of having to check for "contamination" after every build with just a few builds. > You could also try to force a shared library version number > increment. Both sets of libraries have number 1 so are considered That's a totally separate issue. You can't bump the so version for every trial build. > But every downstream packager handles this > differently so there is no point in us doing this. That's one of the lamest excuses I've heard in a long time. Cheers, Roderich
