Re: More info on libldtl failure

[libtool-patches]

On Tue, Jan 30, 2001 at 11:19:27PM +0000, Gary V. Vaughan wrote:
> Hmmm.  I think I can see why this might be... the entire deplib chain
> is followed and loaded for each lt_dlopen()ed module.  Perhaps I need
> to cache previous successes and failures to avoid repetition?  Or
> maybe I just need to provide an option to ignore deplibs (and emulate
> the old behaviour that served us so well before)?

Ha! You think ImageMagick is slow. Wait 'til you try KDE!

BTW, think carefully before caching failures. We were going to suggest
this but I don't know if it is a good idea. What happens if the
library is loaded on the system after the app is started and the first
failure? The app will need to be restarted to work. We could have
timeouts but that is kinda icky.

-- 
albert chin (address@hidden)