DistroWatch typically has a pretty good run down of what each distro has.
Red Hat's run down
Answer from heavyd on Stack ExchangeRed Hat
access.redhat.com › solutions › 38634
What glibc version is shipped with a particular Red Hat Enterprise Linux? - Red Hat Customer Portal
December 2, 2025 - What glibc version is shipped with a particular Red Hat Enterprise Linux update or minor release? We need a later GNU C library for our project but we cannot find it from Red Hat Enterprise Linux. Is there any document about glibc version information?
Fedora Discussion
discussion.fedoraproject.org › project discussion
Glibc version in RHEL 10, or: how to save the 🌍 from mojibake - Fedora Discussion
October 26, 2024 - Hey all TL;DR: I’d like to plead the case for the recently adopted-into-C2y N3366 to make it into RHEL 10, even though this is perhaps a hail mary operation. I’m opening this here because I don’t really know of a better place to start this discussion. But since RHEL essentially branches off from Fedora at some point, it’s a necessary precondition to get it into Fedora anyway – though I have no idea if the decision where to branch off RHEL 10 has already been made (and if so, I assume it cannot...
Is it possible to install older glibc (from Rhel7) on rhel 8?
Install glib-compat. Note that this is only supported minimally, but it exists. And the -compat for 9 is RHEL8’s, and so forth. And it doesn’t help if you depend on other libraries, like openssl. But, really, use a container is the better solution. And even then you have 13 months unless you like paying ELS. More on reddit.com
27
8
May 21, 2023Upgrading glibc to Version 2.39 from 2.34 on Red Hat UBI 9
Don't. You're going the wrong way. More on reddit.com
13
4
December 10, 2024Glibc Error
Hello u/Bad-Mouse Indeed, for rhel8, I can see this version of package, but it should be x86_64 https://access.redhat.com/downloads/content/glibc-common/2.28-251.el8_10.11/x86_64/fd431d51/package For i686, I can see this package only up to rhel6 https://access.redhat.com/downloads/content/glibc-common/2.12-1.212.el6_10.3/i686/fd431d51/package and checking the rhel8 # yum list --showduplicates glibc-common Updating Subscription Management repositories. Last metadata expiration check: 3:20:13 ago on Tue 28 Jan 2025 03:40:18 AM UTC. Installed Packages glibc-common.x86_64 2.28-251.el8_10.5 @rhel-8-for-x86_64-baseos-rpms Available Packages glibc-common.x86_64 2.28-42.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-42.el8_0.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-72.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-72.el8_1.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-101.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-127.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-127.el8_3.2 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-151.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-164.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-164.el8_5.3 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-189.1.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-189.5.el8_6 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-211.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-225.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-225.el8_8.6 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8.7 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8_9.12 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8_9.13 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.2 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.4 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.5 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.11 rhel-8-for-x86_64-baseos-rpms Based on the info above, I believe that your package was installed .. maybe from some 3rd party repo, and unless you really need it, I would recommend you to remove it. But a better advice, if you do have a valid subscription, feel free to open a support case, and also feel free to attach the info above, this will speed up the process. I hope this helps! More on reddit.com
9
2
January 28, 2025Python package requires GLIBC version 2.29 but RHEL 8 cannot support it; attempting to use gcc toolkit but need help
I am trying to use the open source python toolkit, "Aequitas" (GitHub - dssg/aequitas: Bias Auditing & Fair ML Toolkit). One of the functions from the package has a GLIBC-2.29 dependency that my Posit environment won't support (RHEL 8 can only support up to 2.28 (What glibc version is shipped ... More on forum.posit.co
0
0
July 29, 2024Videos
01:40
Red Hat Enterprise Linux 9 Packages - glibc - Full Details of Package ...
Red Hat Enterprise Linux 9 Packages - glibc-common - Full ...
01:40
Red Hat Enterprise Linux 9 Packages - glibc-devel - Full Details ...
01:41
Red Hat Enterprise Linux 9 Packages - glibc-langpack-en - Full ...
Tenable
tenable.com › plugins › nessus › 242114
RHEL 10 : glibc (RHSA-2025:11066)<!-- --> | Tenable®
July 15, 2025 - Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory. Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number. Update the RHEL glibc package based on the guidance in RHSA-2025:11066.
Top answer 1 of 2
22
DistroWatch typically has a pretty good run down of what each distro has.
Red Hat's run down
2 of 2
11
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
LWN.net
lwn.net › Articles › 1021827
Red Hat Enterprise Linux 10 released [LWN.net]
RHEL 10 includes the 6.12.0 kernel, GCC 14.2, GNU Binutils 2.41, GNU C Library (glibc) 2.39, Python 3.12, Perl 5.40, and more. See the release notes for a full list of changes.
GitHub
gist.github.com › richardlau › 6a01d7829cc33ddab35269dacc127680
Linux distributions to kernel and glibc versions map · GitHub
Linux distributions to kernel and glibc versions map - distro-kernel-glibc.md
Reddit
reddit.com › r/redhat › is it possible to install older glibc (from rhel7) on rhel 8?
r/redhat on Reddit: Is it possible to install older glibc (from Rhel7) on rhel 8?
May 21, 2023 -
Hello everyone,
Is there a safe way to install older glibc on redhat 8 so I can get legacy applications that support older rhel 7 to run?
I was able to install the older rpm into a second directory, but when I tried to launch the application, it didn't use that glibc. If I try to ld_library_path, it breaks everything else since, of course, rhel 8 uses newer system glibc. Is there a way around this? Or do I need to use chroot or container of centos7?
Thanks
Top answer 1 of 7
4
Using one container is the best option for that, build one using RHEL7 image and you are good to go.
2 of 7
3
Install glib-compat. Note that this is only supported minimally, but it exists. And the -compat for 9 is RHEL8’s, and so forth. And it doesn’t help if you depend on other libraries, like openssl. But, really, use a container is the better solution. And even then you have 13 months unless you like paying ELS.
Unix Sysadmin
unixsysadmin.com › home › what’s new in rhel 10
Red Hat Enterprise Linux (RHEL) 10
June 25, 2025 - Why? for further information · glibc is at version 2.39 (versus 2.34 in RHEL 9) systemd is at version 256 (versus 252 in RHEL 9.5) python is at version 3.12 (versus 3.9 in RHEL 9) bash is at version 5.2.26 (versus 5.1.8 in RHEL 9) dnf is at ...
Red Hat
learn.redhat.com › t5 › Platform-Linux › How-applications-are-built-for-Red-Hat-8-10-where-glibc-is-2-28 › td-p › 51914
How applications are built for Red Hat 8.10 where glibc is 2.28 ?
June 11, 2025 - Solved: Red Hat 8.10 uses glibc 2.28, which means application built on latest version such as Red Hat 9/10 won't be able to run on Redhat 8.10. I'm
Remi's RPM Repository
rpms.remirepo.net › rpmphp › zoom.php
Packages in Fedora / RHEL / CentOS / EPEL - Package: glibc
Package: glibc · Show more informations from pkgdb · The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for content.
Red Hat
docs.redhat.com › en › documentation › red_hat_enterprise_linux › 7 › html › 7.0_release_notes › sect-red_hat_enterprise_linux-7.0_release_notes-compiler_and_tools-glibc
10.2. GLIBC | 7.0 Release Notes | Red Hat Enterprise Linux | 7 | Red Hat Documentation
10.2. GLIBC | 7.0 Release Notes | Red Hat Enterprise Linux | 7 | Red Hat Documentation
Red Hat
access.redhat.com › articles › rhel10-abi-compatibility
Red Hat Enterprise Linux 10: Application Compatibility Guide - Red Hat Customer Portal
May 20, 2025 - If the application dynamically calls an ELF versioned symbol, it must use the glibc dlvsym API in order to request that specific symbol at that specific version.
Reddit
reddit.com › r/redhat › upgrading glibc to version 2.39 from 2.34 on red hat ubi 9
Upgrading glibc to Version 2.39 from 2.34 on Red Hat UBI 9 : r/redhat
December 10, 2024 - If you gut UBI to bring all of ... easier to use Fedora 40/41 (or CentOS Stream 10) as container base until RHEL 10 is released, then you can use UBI 10....
Reddit
reddit.com › r/redhat › glibc error
r/redhat on Reddit: Glibc Error
January 28, 2025 -
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,
Top answer 1 of 3
3
Hello u/Bad-Mouse Indeed, for rhel8, I can see this version of package, but it should be x86_64 https://access.redhat.com/downloads/content/glibc-common/2.28-251.el8_10.11/x86_64/fd431d51/package For i686, I can see this package only up to rhel6 https://access.redhat.com/downloads/content/glibc-common/2.12-1.212.el6_10.3/i686/fd431d51/package and checking the rhel8 # yum list --showduplicates glibc-common Updating Subscription Management repositories. Last metadata expiration check: 3:20:13 ago on Tue 28 Jan 2025 03:40:18 AM UTC. Installed Packages glibc-common.x86_64 2.28-251.el8_10.5 @rhel-8-for-x86_64-baseos-rpms Available Packages glibc-common.x86_64 2.28-42.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-42.el8_0.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-72.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-72.el8_1.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-101.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-127.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-127.el8_3.2 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-151.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-164.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-164.el8_5.3 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-189.1.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-189.5.el8_6 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-211.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-225.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-225.el8_8.6 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8.7 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8_9.12 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-236.el8_9.13 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.1 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.2 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.4 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.5 rhel-8-for-x86_64-baseos-rpms glibc-common.x86_64 2.28-251.el8_10.11 rhel-8-for-x86_64-baseos-rpms Based on the info above, I believe that your package was installed .. maybe from some 3rd party repo, and unless you really need it, I would recommend you to remove it. But a better advice, if you do have a valid subscription, feel free to open a support case, and also feel free to attach the info above, this will speed up the process. I hope this helps!
2 of 3
2
dnf repoquery --requires glibc.i686 says it needs glibc-common with a matching version-release, but doesn't specify the arch. AFAICS, glibc-common.x86_64 should work fine here, and it does install for me in a container, at least.
Google Groups
groups.google.com › g › linux.redhat › c › 0-HJqGZY5Xw
glibc and RHEL? How do I upgrade the one without messing up the other?
John Oliver wrote: > ["Followup-To:" header set to linux.redhat.] > On Mon, 31 Mar 2008 19:20:47 GMT, W. Dale Hall wrote: >> I'm running RHEL 4 (kernel is apparently this: 2.6.9-67.ELsmp), >> and have found out that my version of glibc is something like >> 2.3.4.
GitHub
gist.github.com › tnk4on › 1cd4c34230dcc44bb9ded278a4a5153f
glibc.x86_64 and glibc.i686 on RHEL · GitHub
$ podman run --rm -it ubi8 bash [root@cb5737b3dbe4 /]# dnf install -y glibc.i686 glibc-devel.i686 gcc -q Installed: binutils-2.30-119.el8.x86_64 cpp-8.5.0-18.el8.x86_64 gcc-8.5.0-18.el8.x86_64 glibc-2.28-225.el8.i686 glibc-devel-2.28-225.el8.i686 ...
Red Hat
docs.redhat.com › en › documentation › red_hat_enterprise_linux › 10 › html-single › considerations_in_adopting_rhel_10 › index
Considerations in adopting RHEL 10 | Red Hat Enterprise Linux | 10 | Red Hat Documentation
Note that this 128-bit long double floating point ABI is incompatible with the floating point ABI used in RHEL 8 and earlier versions. Support for hardware instructions to perform IEEE128 operations is available since IBM POWER9. ... The nscd caching daemon has been removed from RHEL 10. The GNU C Library (glibc) continues to work with the available replacements:
Wikipedia
en.wikipedia.org › wiki › Red_Hat_Enterprise_Linux
Red Hat Enterprise Linux - Wikipedia
2 days ago - RHEL 10 was officially announced on May 20, 2025, at the Red Hat Summit, and uses Linux kernel 6.12.0-55.9.1.el10_0. This release has the codename Coughlan. Red Hat Enterprise Linux 10.0, May 20, 2025, uses Linux kernel 6.12.0-55.9.1.el10_0 ... Red Hat Enterprise Linux 9 was announced at Red Hat Summit on May 10, 2022, and was officially released on May 17, 2022 (2022-05-17). In this version ...
Posit Community
forum.posit.co › posit professional & hosted products
Python package requires GLIBC version 2.29 but RHEL 8 cannot support it; attempting to use gcc toolkit but need help - Posit Professional & Hosted Products - Posit Community
July 29, 2024 - I am trying to use the open source python toolkit, "Aequitas" (GitHub - dssg/aequitas: Bias Auditing & Fair ML Toolkit). One of the functions from the package has a GLIBC-2.29 dependency that my Posit environment won't support (RHEL 8 can only ...
GitHub
github.com › TagStudioDev › TagStudio › issues › 386
[Bug]: GLIBC version mismatch on Rocky/RHEL 9 (requires 2.35) · Issue #386 · TagStudioDev/TagStudio
August 24, 2024 - Failed to load Python shared library '/tmp/_MEIe8CWw8/libpython3.12.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEIe8CWw8/libpython3.12.so.1.0)
Author TagStudioDev