On 11 February 2010 18:49, Andrew Haley <aph@xxxxxxxxxx> wrote: > LD_OPTIONS=-R/usr/local/gcc-4.3.4/lib -L/usr/local/gcc-4.3.4/lib > > is wrong, BTW. You want the -R arg to point to your mpfr's lib as well. > > (This is the -rpath I talked about. We tend to avoid it like the plague, > as it means you can't move libraries.) > > Andrew. I'd specifically put mpir and mpfr libraries in the same place I intended put gcc, so that was not the issue. The problem was I'd put gcc-4.3.4 in the LD_OPTIONS, when it should have been gcc-4.4.3 - I'd transposed the last two digits. To my logic, LD_LIBRARY_PATH should be used when one moves binaries. That is one of its uses. For other reasons tasks is is a disaster. For example, it can't be used if creating binaries with the setuid or setgid bit set. (Well, it can be used, but it will be ignored!) See the link below "Why LD_LIBRARY_PATH is bad" by David Barr. http://xahlee.org/UnixResource_dir/_/ldpath.html Dave
