[gmx-developers] `GLIBC_2.7' not found

Axel Kohlmeyer akohlmey at cmm.chem.upenn.edu
Fri May 21 16:40:33 CEST 2010


>>
>> it is probably easiest to just recompile on the OSC machine.
>
> Or link to a static glibc?

static glibc is a _very_ bad idea. due to choices of how
glibc internals work, static binaries are even less portable
than dynamically linked ones. the most portable binaries
on linux today are compiled on the oldest possible machine
(RHEL 4.x is a good choice) and then linking the glibc and
compiler components libc, libm, libdl, libgcc, libpthreads,
and libstdc++ dynamically and the rest statically.

to get forward compatibility one basically has to copy
the equivalent library binaries to a special directory and
then do:
LD_LIBRARY_PATH=/new/glibc/lib:$LD_LIBRARY_PATH \
/new/glibc/lib/ld-linux.so.2   /path/to/copied/executable  ...

it is a mess...

cheers,
   axel.

> Mark
> --
> gmx-developers mailing list
> gmx-developers at gromacs.org
> http://lists.gromacs.org/mailman/listinfo/gmx-developers
> Please don't post (un)subscribe requests to the list. Use the
> www interface or send it to gmx-developers-request at gromacs.org.
>



-- 
Dr. Axel Kohlmeyer    akohlmey at gmail.com
http://sites.google.com/site/akohlmey/

Institute for Computational Molecular Science
Temple University, Philadelphia PA, USA.



More information about the gromacs.org_gmx-developers mailing list