On 2009-03-23 23:00, Ralf Wildenhues wrote: > Hello Török, > > * Török Edwin wrote on Mon, Mar 23, 2009 at 09:48:33PM CET: > >> When using shared libraries, the libtool wrapper scripts correctly set >> the environment so that the shared library from the build directory is >> used (and not the one from the system). All good. >> >> However when using ltdl to dlopen a shared library, it picks up the >> .la file from /usr/lib instead of the one from the build directory. >> > > Are you using > libtool --mode=execute -dlopen $uninstalled-lib.la $executable >
No, I am simply launching clamscan/clamscan, without the -dlopen arg. > ? > > >> It would be expected that the libtool wrapper script sets the >> environment correctly, so that everything libtool-related is used from >> the build directory, and not from the system. >> > > The libtool wrapper script cannot know which directories it all has to > add to the list of uninstalled places to search, so unfortunately you > have to tell it by using libtool --mode=execute. > > If you agree with this analysis, then I think you can close this as > notabug. > Agreed that it can't know all places, I am just asking that is searches build location in preference of /usr/lib. If I rm libclamunrar* from /usr/lib and /usr/local/lib, then it finds it in the build dir just fine (libclamunrar_iface.la is in same directory as libclamav.so that loads it) Alternatively does ltdl support some way of checking the version of dlopened library? > Cheers, and BTW thank you for providing clear and concise bug reports, > Ralf > Thanks, --Edwin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
