Hello Roger, * Roger Ferrer Ibáñez wrote on Thu, Feb 21, 2008 at 06:54:01PM CET: > > The problem arises when checking the application by means of 'make > check'. If the application has not been installed yet, the dlopened > library is not found (because it still resides somewhere in a given .lib > subdirectory of one builddir) and the test fails.
Try executing $LIBTOOL --mode=execute -dlopen foo/module1.la -dlopen bar/module2.la prg/program instead of prog/program for your tests, with LIBTOOL set appropriately. > I assume that this is the expected behaviour: dlopened shared objects > are not properly found until installed, isn't it? So, I wonder, how is > this issue workarounded? Are testsuites modified so LD_LIBRARY_PATH is > updated to include the proper .lib directory? Doing it manually is another possibility (but not all systems understand LD_LIBRARY_PATH). Cheers, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
