Hi Bob, On 8 Jun 2010, at 23:04, Bob Friesenhahn wrote: > On Tue, 8 Jun 2010, Gary V. Vaughan wrote: >> >> More interesting still: I think things might blow up if the .la files >> have been removed on a platform that does automatic deplib loading for >> runtime linking, say lt_dlopening libpng.dll (which pulls in zlib >> through LoadLibrary without libltdl knowing about it), and then the >> application tries to lt_dlopen libz.dll. It then depends on whether >> the underlying LoadLibrary implementation is smart enough to realise >> that it already has a copy of libz in memory and returns a handle to >> it without trying to reload another copy first... this would be an >> interesting test to have in the next release to see what feedback it >> brings. > > Obviously this is already working fine. Windows LoadLibrary() is smart > enough to know what it has already loaded. The unloading sequence is much > more interesting since something could be unloaded which is still being used.
Looks like another interesting test case for 2.2.10 to me :) Do you feel motivated to write it? Or at least add a description to the TODO file in the tests directory? Cheers, -- Gary V. Vaughan (g...@gnu.org) _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
