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.