On Thu, 10 Feb 2005, Greg A. Woods wrote:

> > This is normal libtool behavior.
>
> If that's the way libtool is now working all of the time then it is broken.

I thought so too, but there's a real problem here:  ensuring that libraries
do not accidentally touch installed previous versions of the same libraries.

Remember that LD_LIBRARY_PATH handling happens *after* rpaths are consulted.
So, if you have a library in your build tree whose soname matches an
installed one (say, when updating a package....), the installed one will be
used -- not the in-tree one.

That's not the only problem, but it's the main one.  It gets even more hairy
when trying to link dependent shlibs in the same build tree, and you have
libs of the same soname installed.  -rpath-link isn't enough in this case;
you can end up with major linker botches.  Relinking just-in-time for
installation fixes this, because you're installing in the correct order
(just as they were built in the correct order in order to build properly).

-- 
-- Todd Vierling <tv@duh.org> <tv@pobox.com>