David Faure wrote:

> On Monday 22 November 2004 14:44, Michael Matz wrote:
> 
>>Hi,
>>
>>On Sun, 21 Nov 2004, Thiago Macieira wrote:
>>
>>
>>>My solution consists in:
>>>1) adding the --enable-new-dtags flag to the linker, if supported. This 
>>>makes GNU ld emit RUNPATH directives as well as RPATH. The consequence is 
>>>twofold:
>>>	a) RPATH is ignored
>>>	b) RUNPATH is overrideable by LD_LIBRARY_PATH at run-time
>>>
>>>2) making libtool's stub script use LD_LIBRARY_PATH as well as relinking. 
>>
>>This should do no harm.  It changes a bit the way how you can call the 
>>lt-* binary.  After calling the script once it was self-contained (i.e. 
>>contained all relevant RPATHs), so it was possible to call the lt-* binary 
>>directly.  Now you really have to go through the script for setting 
>>LD_LIBRARY_PATH.
> 
> 
> Ouch, that means no more "gdb .libs/lt-foobar core.12345" then...
> Well, I guess a "make install" (of the libs) makes it work, since the installed libs 
> will then match the ones used by .libs/lt-foobar.
> 

I think Thiago's solution is very elegant, and libtool's documentation 
about debugging should work with the patch. It's about no to run the 
lt-executable directly, but run gdb via the wrapper script.

See:
http://www.gnu.org/software/libtool/manual.html#SEC11

György