Q skrev 2010-12-17 22:57: > I assume this occurs with anything you compile from source, that it > defaults to /usr/local/lib unless you tell it otherwise, causing > problems if older versions have been installed elsewhere by other means. > (I make this assumption on the fact that all the libraries in > /usr/local/lib look to be for the few things I've compiled myself rather > than using a package manager for.)
Yes, source packages using an autoconf configure script usually defaults to /usr/local. > How does one solve this problem -- put a link in /usr/lib pointing to > the actual library in /usr/local/lib, or at compile time tell it to put > the lib in /usr/lib? In either case, how does one do that? Often it's enough to just put /usr/local/lib first in LD_LIBRARY_PATH: export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH Then the libraries in /usr/local/lib will be used instead of the ones in /usr/lib. You might also need to set PKG_CONFIG_PATH to /usr/local/lib/pkgconfig before running configure in packages that depends on the libs in /usr/local. The other option is to install the libs in /usr/lib. This is done with the --prefix option to configure: ./configure --prefix=/usr This might however mess up the package system of your linux distribution. /Andreas ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
