Nick Bowler wrote: > Won't the problem of setting up shared library search paths be solved > if you just link the test program using libtool, so the usual wrapper > programs are generated to setup the platform-specific search paths?
Most packages that *use* a library do so without using libtool. For example, coreutils uses several libraries (libintl, libiconv, libgmp, selinux, openssl, systemd) but does not use libtool. It simply passes -L and -l (and -Wl,-rpath,...) options directly to the compiler. Therefore, using libtool for 'installcheck' is the wrong approach, because it's not what packages do when they use the library. In particular, problems with library dependencies are likely to go unnoticed if you link with libtool — because libtool uses .la files which contain information about library dependencies, and normal users of the library will not use this information. Bruno
