RE: Subversion Build Issues - 1.10.6
From: Sanad Majid <sanad.majid_at_LumaCyte.com>
Date: Fri, 26 Jun 2020 20:23:42 +0000
Thank you Daniel, Thorsten and Nathan. After uninstalling 'libsvn1' and 'libapache2-mod-svn', I was able to build Subversion.
WARNING: This message originated from an external sender.
Thorsten wrote on Fri, 26 Jun 2020 10:24 +0200:
It's a known issue on Debian systems; I predicted it in my first reply.
https://bugs.debian.org/291641 libtool: Checks dependencies of shared libraries without honouring RPATH
> It assume that this is a an old version of svn which was already
That was probably installed by a package, rather than by someone manually building from source.
> So a few things you can try from easy to complicated:
- Look for new Subversion packages that you can install on top of the
> - try to compile subversion on a fresh setup
Either by uninstalling the "libsvn1" and "libapache2-mod-svn" packages (which you probably have installed), or by temporarily removing the *.so files installed by those packages for the duration of the build/install process. (Renaming those files, or moving them to another directory, would suffice.)
In the temporary removal case, you'll want to also do that to *.so files shipped by other Subversion-related packages. Precisely, we're talking about the set of binary packages built from the «subversion» source package, i.e., those listed by «aptitude search '~i ~e subversion'», but it might be easier for you to find the relevant packages by going through the list of installed packages that depend on libsvn1. Once you have identified the relevant packages, take them through «dpkg -L», or just uninstall them _en masse_.
By the way, given that you're switching from (probably) a Debian package's libsvn_foo.so to self-built libsvn_foo.so, see:
> - fiddle with the linker so that the other svn does not get picked up
This is an archived mail posted to the Subversion Users mailing list.