hi,
is it possible to have multiple glibc version one is running glibc-2.12.x86_64 and the other one is glibc-2.5.x86_64.

Thanks advance

Yes, it is possible. But it's definitely not good. I would remove the older one and then reinstall the newer one.

Thanks for the replied.
removing existing one will destroy all shared libraries associated in it. linux will not boot.

What distro are you running?

What is depending on the old, and maybe has not been updated to depend on the new?

Thanks for the replied.

I'm running centos 6.6 and i'm need to load also lower glibc from atleast centos 5 below

Have you thought of setting yourself up a VM environment, so you can run multiple of glib without worry? Or if you are installing them from source, you could try to isolate each version in a pool setup in /opt for example using prefix=/opt, then point to each one as needed.

You can also use LXC to create containers with different versions of glib.

you can also use a build forder and install it out of system

i some times need to do this for gimp-development code

sometimes the version required is very new


i use a "config.site " file for autotools and build the software in a folder that IS NOT!!!! IN THE SYSTEM $PATH !!!!!

but BE WARNED

Installing multiple glibc or deviating from one provided by distro is asking for trouble.

I tried to install compile glibc 2.4 on existing glibc 2.12 and it prompted me on these errors. any thoughts on this. TIA


checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for gcc... gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for ranlib... ranlib
checking whether as is GNU as... yes
checking whether ld is GNU ld... yes
checking for as... as
checking version of as... 2.20.51.0.2, bad
checking for ld... ld
checking version of ld... 2.20.51.0.2, bad
checking for pwd... /bin/pwd
checking for gcc... gcc
checking version of gcc... 4.4.7, ok
checking for gnumake... no
checking for gmake... gmake
checking version of gmake... 3.81, ok
checking for gnumsgfmt... no
checking for gmsgfmt... no
checking for msgfmt... msgfmt
checking version of msgfmt... 0.17, ok
checking for makeinfo... no
checking for sed... sed
checking version of sed... 4.2.1, ok
checking for autoconf... autoconf
checking whether autoconf works... yes
configure: error:
*** These critical programs are missing or too old: as ld
*** Check the INSTALL file for required versions.

that is all I can see, what as is I have no idea, but ld, states that it too is bad. I'd start there.

if you are using a out of path build folder you also NEED to build and install to that folder ALL!!!!! the prerequisites

and this might be 80% of the operating system for some things
or one or two programs

When you uninstall the old version and reinstall the newer version, it just updates the generic library links to point to the new versions, which are backwards compatible. If it were any other way the result would absolute chaos.