[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: broken libtool on freebsd

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-06-11 19:21:54 CEST

Ben Collins-Sussman <sussman@collab.net> writes:

> Just to verify this, I'll build a shared binary, and then run 'ldd' on
> .libs/lt-svn. Sure enough, all of the libraries resolve to ones in
> /usr/local/lib, instead of the freshly-built ones in my source tree.
> This is *not* how libtool is supposed to work.
> Maybe libtool is somehow invoking the linker incorrectly, or some kind
> of -rpath switch isn't working? Maybe my system is horked? Does
> anyone else ever see this problem?

It works for me on my Linux box. I build shared most of the time.

The lt-svn executable is created when you run the clients/cmdline/svn
script. If you delete lt-svn and run the svn script, lt-svn should be
recreated. The script contains a 'relink_command' that specifies the
necessary libraries and rpath options. Looking at that command I see
relative path libraries such as


absolute path libraries such as


and --rpath options such as

-Wl,--rpath -Wl,/home/pm/sw/subversion/obj/subversion/libsvn_repos/.libs

As far as I can see the relative path libraries are the explicit
dependencies, and the absolute path libraries arise when one
Subversion library depends on another. Within my build tree, any
Subversion libraries that are linked to other Subversion libraries
resolve those links within the tree.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 11 19:22:29 2002

This is an archived mail posted to the Subversion Dev mailing list.