Re: Libtool incorrectly adds dependency libs to $deplibs

[Albert Chin]

On Wed, Mar 24, 2004 at 03:10:44AM +0000, Scott James Remnant wrote:
> On Sun, 2004-02-08 at 23:08, Albert Chin wrote:
> 
> > On Sun, Feb 08, 2004 at 08:40:20PM +0000, Scott James Remnant wrote:
> > > On Sun, 2004-02-08 at 19:31, Albert Chin wrote:
> > > 
> > > > When libtool adds a .la file to $deplibs, it first adds the library
> > > > name to $deplibs and if $link_all_deplibs=yes, each dependency library
> > > > is added to the library search path with -L. However, when libtool
> > > > does this, it places non-duplicated -L paths *before* other $deplibs
> > > > entries. Why doesn't libtool add the new -L paths *before* the
> > > > library name entry from the .la file? If we agree this is the correct
> > > > behavior, patch below.
> > > > 
> > > Could you give an example of what you mean...  Preferably one showing
> > > the current behaviour and how it breaks something along with your
> > > modified behaviour and how/why it fixes it.
> > 
> > Say I'm trying to build libpng-1.2.4 on a Solaris 9/SPARC machine with
> > the Sun C compiler:
> *snip*
>
> I'm still not clear from this exactly what's breaking because of this;
> have you got an example which actually causes something to demonstrably
> break (ie. link the wrong thing, or flat-out fail to link)?

It's been too long but I think I was compiling KDE with an updated
libtool-1.5 that caused the breakage. Anyway, just from my examples,
what is the misunderstanding?

Adding to $deplibs is _always_ additive, which is wrong. If I:
  $ libtool -L/abc -L<path> -L/def ... -l[library found in <path>]
why should -L paths from dependency_libs in the -l libraries come
_before_ libraries I specify (i.e. -L/abc -L<path> -L/def)?

-L paths from dependency_libs should on the command-line _just before_
the -l library.

-- 
albert chin (address@hidden)