Re: References to old db in shared libs and executables

On Mon, Mar 10, 2003 at 16:13 +0100, Tobias Ringstrom wrote:

> On Mon, 10 Mar 2003, Jens-Uwe Mager wrote:
>
> > I believe it is problem that occurs because libtool adds a -L/usr/lib
> > before the user supplied -L args to the linker command line. This pretty
> > much inhibits the use of -ldb, as this will always match the db library
> > in /usr/lib before any user supplied -L arguments. It would only work if
> > specified with an explicit -ldb4 or by using the .la file to instruct
> > libtool exactly about the library to link against. Welcome to the realms
> > of .so hell.
>
> Yes you are right. It's clearly visible if you remove the --silent from
> libtool. But why is that a .so problem and not a libtool bug?

The reference to .so hell was me venting. While installing subversion
and getting the python bindings to work I pretty much felt like a user
installing two packages under Win95 or so with conflicting DLL's. The
technical reasons might be different, the feeling was the same. I am sad
that a Linux machine makes me feel like this.

-- 
Jens-Uwe Mager	<pgp-mailto:F476EBC2>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org