broken libtool on freebsd

Hey Garrett, as fellow FreeBSD user, I thought you could shed some
light on this question. Maybe others can comment as well.

I have this awful resistance to building svn shared and installing it;
I usually just build statically and make /usr/local/bin/svn a symlink
to the static binary in my source tree.

The reason for this is that libtool 1.4 seems to have a wonky behavior
on FreeBSD: whenever something is linked during a compile, libtool
will use whatever libsvn_* libraries are installed in /usr/local/lib/,
no matter what. On other platforms, apparently this isn't true. Greg
Stein builds shared all the time, and never runs into this problem.

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?

(I'm using FreeBSD 4.5-STABLE.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 11 17:08:00 2002