Greg Hudson <ghudson@MIT.EDU> writes:
> On Mon, 2002-09-16 at 17:54, Greg Stein wrote:
> > Sure. 'make check' works regardless of how you build. Ben was doing it all
> > the time before he discovered that an LD_LIBRARY_PATH was monkeying up his
> > shared build.
>
> On Linux and some other systems (not Solaris), run paths in the binary
> override LD_LIBRARY_PATH. So until you install, the binaries will (I
> think) choose previously installed libraries over the ones in the build
> tree. "make check" should work if you've never installed Subversion
> before, though.
No, on Linux "make check" always works. We use libtool and that means
that the executable subversion/clients/cmdline/svn is a script that
will relink against the build libraries to produce an executable and
run that. So "make check" uses the build libraries whether or not you
have installed libraries.
I use a shared build on Linux all the time. I use a configure prefix
of /usr/local/subversion and my build produces
$ file subversion/clients/cmdline/svn
subversion/clients/cmdline/svn: Bourne shell script text executable
$ ldd subversion/clients/cmdline/.libs/lt-svn | grep delta
libsvn_delta-1.so.0 => /home/pm/sw/subversion/obj/subversion/libsvn_delta/.libs/libsvn_delta-1.so.0 (0x40086000)
$ ldd subversion/libsvn_delta/.libs/libsvn_delta-1.so | grep subr
libsvn_subr-1.so.0 => /home/pm/sw/subversion/obj/subversion/libsvn_subr/.libs/libsvn_subr-1.so.0 (0x40011000)
--
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 17 23:41:13 2002