🌐
GitHub
gist.github.com › tnk4on › 1cd4c34230dcc44bb9ded278a4a5153f
glibc.x86_64 and glibc.i686 on RHEL · GitHub
glibc.x86_64 and glibc.i686 on RHEL. GitHub Gist: instantly share code, notes, and snippets.
🌐
GitHub
gist.github.com › wagenet › 35adca1a032cec2999d47b6c40aa45b1
glibc Versions - Gist - GitHub
glibc Versions. GitHub Gist: instantly share code, notes, and snippets.
Discussions

[Bug]: GLIBC version mismatch on Rocky/RHEL 9 (requires 2.35)
Checklist I am using an up-to-date version. I have read the documentation. I have searched existing issues. TagStudio Version Alpha v9.3.2 Operating System & Version Rocky Linux 9.4 Description Por... More on github.com
🌐 github.com
3
August 24, 2024
Glibc version in RHEL 10, or: how to save the 🌍 from mojibake - Fedora Discussion
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 ... More on discussion.fedoraproject.org
🌐 discussion.fedoraproject.org
1
October 26, 2024
Python 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
🌐 forum.posit.co
0
0
July 29, 2024
VS Code 1.66 requires GLIBC 2.25 on RHEL 7
VS Code version: code-1.66.0-1648620680 OS: Red Hat Enterprise Linux 7.9 Running yum update on RHEL 7 produces an error: Error: Package: code-1.66.0-1648620680.el7.x86_64 (code) Requires: libc.so.6(GLIBC_2.25)(64bit) According to https:/... More on github.com
🌐 github.com
20
March 31, 2022
🌐
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
🌐
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
In Red Hat Enterprise Linux 7, the glibc libraries (libc, libm, libpthread, NSS plug-ins, and others) are based on the glibc 2.17 release, which includes numerous enhancements and bug fixes relative to the Red Hat Enterprise Linux 6 equivalent.
🌐
GitHub
gist.github.com › jcelerier › 8cd9a35994b0f15380b3070d40b6aabc
glibc Versions · GitHub
List of oldest supported version of top 10 Linux Distros and their glibc version according to distrowatch.com.
🌐
Red 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...
🌐
Xpack-dev-tools
xpack-dev-tools.github.io › xpack-build-box › docs › end-of-support
End-of-support schedule | XBB - The xPack Build Box
February 21, 2025 - registry.access.redhat.com/rhel7 - GLIBC 2.17, 2012-2019 (2024), kernel 3.10 <-- XBB v3.3
Find elsewhere
🌐
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.
🌐
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 ... 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 ......
🌐
GitHub
github.com › microsoft › vscode › issues › 146390
VS Code 1.66 requires GLIBC 2.25 on RHEL 7 · Issue #146390 · microsoft/vscode
March 31, 2022 - VS Code version: code-1.66.0-1648620680 OS: Red Hat Enterprise Linux 7.9 Running yum update on RHEL 7 produces an error: Error: Package: code-1.66.0-1648620680.el7.x86_64 (code) Requires: libc.so.6(GLIBC_2.25)(64bit) According to https:/...
Author   microsoft
🌐
GitHub
github.com › mattermost › desktop › issues › 3353
[Bug]: RHEL 8 cannot run v5.11 due to missing GLIBC 2.29 · Issue #3353 · mattermost/desktop
February 24, 2025 - This issue reproduces on the most recent stable version, or the most recent prerelease version of the Mattermost Desktop App. I have read the contribution guidelines. mattermost-desktop-5.11.0-1.x86_64 Won't run on Red Hat 8.10 Due to GLIBC
Author   mattermost
🌐
Red Hat
docs.redhat.com › en › documentation › red_hat_enterprise_linux › 9 › html-single › 9.0_release_notes › index
9.0 Release Notes | Red Hat Enterprise Linux | 9 | Red Hat Documentation
Most distributions send locale environment variables by default and accept them on the server side. However, this meant that logging in through SSH from clients that used locales other than C or C.UTF-8 to servers that did not have the glibc-langpack-en or glibc-all-langpacks package installed resulted in degraded user experience.
🌐
GitHub
github.com › Microsoft › napajs › issues › 192
Error: /lib64/libc.so.6: version `GLIBC_2.14' not found on RED-Hat(RHEL-6.5) Linux · Issue #192 · microsoft/napajs
February 8, 2018 - I’m using node module napajs on RED-Hat(RHEL-6.5) Linux machine. On Linux machine, node version is 6.10.0 and gcc version is 4.4.7. I wrote a simple node program using napajs module. When I execute this program, first I faced GLIBC-2.14 library issue.
Author   microsoft
🌐
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.
🌐
GitHub
gist.github.com › xuyang2 › 3ab29d04ca47738d59fac5647d9bf0e9
glibc-versions.md · GitHub
glibc-versions.md · see · https://sourceware.org/glibc/wiki/Glibc Timeline · https://distrowatch.com/table.php?distribution=centos · https://distrowatch.com/table.php?distribution=redhat · https://distrowatch.com/table.php?distribution=sle · https://distrowatch.com/table.php?distribution=debian ·
🌐
GitHub
github.com › nodejs › node › issues › 48453
RHEL 7.9 GLIBC Errors · Issue #48453 · nodejs/node
June 13, 2023 - Linux user@company.net 3.10.0-1160.80.1.el7.x86_64 #1 SMP Sat Oct 8 18:13:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ... # install nvm using readme guide $ nvm install --lts Installing latest LTS version. v18.16.0 is already installed. Now using node v18.16.0 (npm v) node: /lib64/libm.so.6: version `GLIBC...
Author   nodejs