[EMAIL PROTECTED] writes: > The LD_LIBRARY_PATH variable is for ELF systems to find shared > libraries at run-time. The LIBRARY_PATH variable, on the other hand, > is a gcc setting that lets it find libraries at link-time. It's a > colon-separated path that fills in a bunch of '-L' options. Other > linkers have similar extensions -- LPATH, LOPTS, etc.
OK, thanks. I was confused because I knew about LD_LIBRARY_PATH, but not LIBRARY_PATH. > I've used this trick successfully in building rpm's containing > multiple, interdependent shared libraries. The spec file cooks up a > custom LIBRARY_PATH setting before invoking 'make DESTDIR=foo > install'. The name of the game in spec file writing is to minimize > the patch set required to build the package, so Makefile hackery is > discouraged. Agreed -- the same is true with Debian -- minimizing the Debian diff is a good idea, all other things being equal. In any case, thanks so much. I'll try this -- it looks like a good solution. -- Rob Browning rlb @defaultvalue.org, @linuxdevel.com, and @debian.org Previously @cs.utexas.edu GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
