You can find the official glibc versions for CentOS on the CentOS mirror sites.
For example
- http://centos.mirror.iweb.ca/5.4/updates/i386/RPMS/
- http://centos.mirror.iweb.ca/4.8/updates/i386/RPMS/
linux - Install glibc 2.15 in Red Hat 6.5 - Stack Overflow
dependencies - RHEL 6 - how to install 'GLIBC_2.14' or 'GLIBC_2.15'? - Stack Overflow
software installation - Install older version of GLibc on RHEL - Unix & Linux Stack Exchange
Glibc Error
You can find the official glibc versions for CentOS on the CentOS mirror sites.
For example
- http://centos.mirror.iweb.ca/5.4/updates/i386/RPMS/
- http://centos.mirror.iweb.ca/4.8/updates/i386/RPMS/
If you are absolutely sure you need it, you have two choices:
- use a different distribution that has the version you need (perhaps in a VM on top of your CentOS)
- Compile everything manually (I'd install rpm-build and use
make rpm, but this might
a) break dependencies in the system, and
b) be a pretty complicated task to do, since the new version of glibc will require a lot of other prerequisites)
Can I install glibc from some repo?
Not likely: distributions usually don't ever update the major/minor version of glibc from the one they originally shipped with, because the likelihood of breaking applications is too great.
You may have to build glibc-2.15, or better current glibc-2.24 from source and install it into non-default location. See this answer.
If you are registered to satellite , Just run :
yum install glibc
this should take care of all . If you are installing using rpms manually, you need dependent rpms as well.
Hope this helps.. Good luck.
This often occurs when you build software in RHEL 7 and try to run on RHEL 6.
To update GLIBC to any version, simply download the package from
https://ftp.gnu.org/gnu/libc/
For example glibc-2.14.tar.gz in your case.
1. tar xvfz glibc-2.14.tar.gz
2. cd glibc-2.14
3. mkdir build
4. cd build
5. ../configure --prefix=/opt/glibc-2.14
6. make
7. sudo make install
8. export LD_LIBRARY_PATH=/opt/glibc-2.14/lib:$LD_LIBRARY_PATH
Then try to run your software, glibc-2.14 should be linked.
Naive question: Is it possible to somehow download GLIBC 2.15, put it in any folder (e.g. /tmp/myglibc) and then point to this path ONLY when executing something that needs this specific version of glibc?
Yes, it's possible.
Is it possible you're using a RHEL 6-Beta DVD on a RHEL 6.0 system?
It looks like RHEL 6 has always had glibc 2.12 but the beta release had glibc 2.11. I really can't find a definitive source that says what the 6-Beta had but find mentions of 2.11 on 6-Beta around the web like here and here. All of the CentOS src.rpms for 6.0 to 6.3 are glic 2.12 so the final release has always had 2.12.
Is it possible you initially installed from the 6-beta DVD but have upgraded to a newer RHEL release since then? If so, you really can't use the packages from an older RHEL DVD. If you're just trying to install gcc, you can run yum install gcc to get GCC 4.4.x. In general, installing through yum is preferred over the DVD since yum will automatically fetch the latest RPMs whereas the DVD might have an older version that has some bugs. If you really want the DVD method, you'll need to get a DVD that matches the RHEL 6 release you have installed.
cat /etc/redhat-release will tell you what version of RHEL you're running. I'm guessing you're on 6.0 since the version of glibc currently installed is from November 2010 (you should look in to upgrading to 6.3 at some point). As for how to tell what version the DVD is, I'm guessing if you boot from it, it will say RHEL 6 Beta or something on the splash screen. Maybe read the docs on the DVD to see if it references being a beta?
You could download the source RPM and rebuild it so it uses the system libs you have (2.12).
I’m trying to update a RHEL 8 machine with dnf and I’m getting a dependency error for glibc-2.28-251.el8_10.11.i686
It needs glibc-common-2.28-251.el8_10.11.i686.
If I browse Red Hat’s baseos repository, I don’t see it in there. Do you think maybe it hasn’t been added yet or do I have something else wrong? Thanks,