Re: problems with LD_LIBRARY_PATH and libtool wrapper

[Ralf Wildenhues]

Hi Dan,

* Dan McMahill wrote on Wed, Aug 13, 2008 at 11:06:41PM CEST:
> I have a problem with the LD_LIBRARY_PATH handling inside of the libtool  
> wrapper.  I see a line like:
>
> # Add our own library path to LD_LIBRARY_PATH
> LD_LIBRARY_PATH="/usr/pkg/lib:/home/dan/src/myprog/libmine/.libs:$LD_LIBRARY_PATH"
>
> in /home/dan/src/myprog/src/myprog which is the libtool wrapper.
>
> The problem is I may have an out of date libmine installed in  
> /usr/pkg/lib and at runtime I pick that one up instead of the one in  
> /home/dan/src/myprog/libmine/.libs.  This has caused me great confusion  
> a couple of times when I absolutely could not correlate the behavior of  
> the program with the sources in ../libmine because of course they didn't  
> match.
>
> It seems that we want to make sure any ".libs" directories appear first  
> in LD_LIBRARY_PATH.
>
> Am I missing something obvious here?

Could be.  Does myprog have an
  myprog_LDADD = ../libmine/libmine.la

line, and can you show the libtool link command lines for both the
library and the program plus all of their output when executed?

Thanks,
Ralf