[Bug]: GLIBC version mismatch on Rocky/RHEL 9 (requires 2.35)
Glibc version in RHEL 10, or: how to save the 🌍 from mojibake - Fedora Discussion
Python package requires GLIBC version 2.29 but RHEL 8 cannot support it; attempting to use gcc toolkit but need help
VS Code 1.66 requires GLIBC 2.25 on RHEL 7
DistroWatch typically has a pretty good run down of what each distro has.
Red Hat's run down
Edit: The RedHat documentation used to list the version of the libraries they included. They have since removed that information.
This data is from distrowatch. Sorry for the sideways scroll and long ASCII text. StackOverflow doesn't support Markdown Tables.
| Package | RHEL-8.4 | RHEL-7.9 | RHEL-6.9 | RHEL-5.11 | RHEL-4.8 | RHEL-3.9 | RHEL-2.1 | 9 | 8.0 | 7.3 | 7.2 | 7.1 | 7.0 | 6.2 | 6.1 | 6.0 | 5.2 | 5.1 | 5.0 | 4.2 |
| | | | | | | | | shrike | psyche | valhalla | enigma | seawolf | guiness | zoot | cartman | hedwig | apollo | manhattan | hurricane | biltmore |
| glibc (2.34) | 2.28 | 2.17 | 2.12 | 2.5 | 2.3.4 | 2.3.2 | 2.2.4 | 2.3.2 | 2.2.93 | 2.2.5 | 2.2.4 | 2.2.2 | 2.1.92 | 2.1.3 | 2.1.2 | 2.1.1 | 2.0.7 | 2.0.7 | 2.0.5c | -- |
It used to be available from RedHat documentation: RHEL 6 RHEL 7
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,
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.