Hello David, Alberto, * Alberto Luaces wrote on Mon, Dec 28, 2009 at 01:45:16PM CET: > David Bruce writes: > > > OK, I can get it to work post-installation with either LD_LIBRARY_PATH > > or the ldconfig+/etc/ld.so.conf mechanism. What I want to learn is > > the "right" way to do this as a programmer/packager from an autotools > > perspective so that a user can do "./configure; make; sudo make > > install" on my lib package (libt4kcommon)and on my executable package > > (tuxmath) and have it work. > > This is user responsibility; if the user installs a library in some > directory, the user has also to tell its system to look for libraries > there. For example, in my Debian system, /usr/local/lib is included by > default in the directories' list to be looked at when searching libs.
An alternative is to use something like the gnulib module 'havelib' which also takes care to add run paths to libraries not in places the runtime linker searches. (libtool does it too, but that may be overkill for this use alone, in the tuxmath package.) Otherwise, using AC_CHECK_LIB is fine. Cheers, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
