I don’t have a solution for this one, but I managed to go ahead with different settings. I got this package from a colleague that is supposed to be of general interest. It does come with a binary inside, and when you run it, you get the above GLIBC error. A little bit of googling will point onto python as a culprit of the error, and since I have a local python (my pyyyython) that is working fine and it is easy to maintain, I used that one to run the code. The point is, anyway, what to do if you don’t have “my” python.
You could download and compile your glibc. That worked fine in my CentOS 7 case:
mkdir ~/glibc_install; cd ~/glibc_install wget http://ftp.gnu.org/gnu/glibc/glibc-2.XX.tar.gz tar zxvf glibc-2.XX.tar.gz cd glibc-2.14 mkdir build cd build ../configure --prefix=/opt/glibc-2.14 make -j4 make install export LD_LIBRARY_PATH=/opt/glibc-2.XX/lib
Note that XX is the GLIBC version. After the install, I could link the new library with the old one, something like
ln -s /opt/glibc-2.XX/lib/libc-2.XX.so /usr/lib64/libc.so.6
Be aware that you can screw up your system if you delete libc.so! But don’t panic if you already did, ldconfig will reconfigure your libraries and bring you back to a running system. Or I think it will 😛 …