libmv and other libs in .../lib/gcc-lib/x86_64-open64-linux/

Discussion created by yoyoyoman on May 18, 2010
Latest reply on May 18, 2010 by dgilmore
Problems with portability by libs in .../lib/gcc-lib/x86_64-open64-linux/


When compiling several applications, e.g. GROMACS (www.gromacs.org), I noticed that the built executables always need some libraries in .../lib/gcc-lib/x86_64-open64-linux/ (where ... is the directory in which I installed open64). If the compiler is located elsewhere, the compiled excutable will not run.

This severely hampers the portablility of the applications. Even when compiling GROMACS statically, there still remains the libmv.so.1 which has to be read from the fixed installation path of open64. Is there a simple solution for this problem?