2009/3/5 Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>: >> I have two stages where I must be able to compile, link and run code >> using the lib: >> A. conftest code at configure time >> B. the build product at runtime (of course) >> >> B is working by means of autoconf/libtool. > > Correct. > >> A is giving me problems because afaict as described I must inject -R >> or -rpath depending on the environment. >> >> Presumably I should be able to use LD_LIBRARY_PATH instead to solve A, >> which afaict should be quite portable. > > Good idea. But the variable may be called differently on other systems. > If you use libtool, and ensure its tests are run before your link test, > you can inspect the $shlibpath_var variable for the name of the variable > to use. This sounds promising. Thanks! -Frank _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
