Check it is actually needed

Firstly check the python application as it could be out of date and is probably misreading the glibc version. CentOS shows the base version as installed and is patched to keep up with changes and it could just be a case of fixing the version that is being looked for in the code as a quick fix, but if the application is being actively developed you need to let the developers know or fork it for yourself if you can.

An up to date glibc on CentOS 7 should be 2.17-196.el7_4.2

If it is needed, Containerise

If it's absolutely necessary to run this application, the official RHEL approach would be to containerize, but you would still need to provide a working glibc, which wouldn't be possible with stock CentOS 7.

As a last resort, install glibc in a nonstandard location

If this isn't viable, and as an absolute last resort, it is possible to install a newer version of glibc than 2.18 as that is 9 years old now and glibc has been updated for several vulnerabilities and I'm not sure off the top of my head if it will build with the version of make in CentOS 7, but any newer version should work as follows:

  • This can potentially affect the functionality of your computer so make sure you know what you are doing

You can build the version of glibc you require elsewhere on your server and add it to LD_LIBRARY_PATH for the application. Note this must only be done for the application only.

wget http://ftp.gnu.org/gnu/glibc/glibc-2.18.tar.gz
tar zxvf glibc-2.18.tar.gz
cd glibc-2.18
mkdir build
cd build
../configure --prefix=/opt/glibc-2.18
make -j4
sudo make install

Then to run a binary you need to use patchelf to update its interpreter

patchelf --set-interpreter /opt/glibc-2.18/lib/ld-linux-x86-64.so.2 program_you_are_running

And you need to enable it to find the new glibc library, either by

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/glibc-2.18/lib

Or you can use patchelf to update the binary's rpath (you can combine this with the previous pathelf command)

patchelf --set-rpath /opt/glibc-2.18/lib:/usr/lib64 program_you_are_running

If you change LD_LIBRARY_PATH don't export it for the whole system because all the binaries unmodified by patchelf will segfault.

/opt is the standard place to install third-party applications and libraries but you can use any path away from the system paths.

Answer from Simon Greenwood on serverfault.com
🌐
Liquid Web
liquidweb.com › home › how to update the glibc (gnu libc) in centos / red hat
How to Update the glibc (GNU libc) in CentOS / Red Hat | Liquid Web
December 3, 2024 - In this case, yum is the rpm-based package manager for both Red Hat and CentOS, -y, –assumeyes gives yes as an answer to any question which would be asked by running the command, update is for updating the package, and glibc is the package you’re updating!
🌐
Server Fault
serverfault.com › questions › 894625 › safely-upgrade-glibc-on-centos-7
centos7 - safely upgrade glibc on CentOS 7 - Server Fault
Top answer
1 of 3
23

Check it is actually needed

Firstly check the python application as it could be out of date and is probably misreading the glibc version. CentOS shows the base version as installed and is patched to keep up with changes and it could just be a case of fixing the version that is being looked for in the code as a quick fix, but if the application is being actively developed you need to let the developers know or fork it for yourself if you can.

An up to date glibc on CentOS 7 should be 2.17-196.el7_4.2

If it is needed, Containerise

If it's absolutely necessary to run this application, the official RHEL approach would be to containerize, but you would still need to provide a working glibc, which wouldn't be possible with stock CentOS 7.

As a last resort, install glibc in a nonstandard location

If this isn't viable, and as an absolute last resort, it is possible to install a newer version of glibc than 2.18 as that is 9 years old now and glibc has been updated for several vulnerabilities and I'm not sure off the top of my head if it will build with the version of make in CentOS 7, but any newer version should work as follows:

  • This can potentially affect the functionality of your computer so make sure you know what you are doing

You can build the version of glibc you require elsewhere on your server and add it to LD_LIBRARY_PATH for the application. Note this must only be done for the application only.

wget http://ftp.gnu.org/gnu/glibc/glibc-2.18.tar.gz
tar zxvf glibc-2.18.tar.gz
cd glibc-2.18
mkdir build
cd build
../configure --prefix=/opt/glibc-2.18
make -j4
sudo make install

Then to run a binary you need to use patchelf to update its interpreter

patchelf --set-interpreter /opt/glibc-2.18/lib/ld-linux-x86-64.so.2 program_you_are_running

And you need to enable it to find the new glibc library, either by

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/glibc-2.18/lib

Or you can use patchelf to update the binary's rpath (you can combine this with the previous pathelf command)

patchelf --set-rpath /opt/glibc-2.18/lib:/usr/lib64 program_you_are_running

If you change LD_LIBRARY_PATH don't export it for the whole system because all the binaries unmodified by patchelf will segfault.

/opt is the standard place to install third-party applications and libraries but you can use any path away from the system paths.

2 of 3
4

In the end,I did not have to upgrade GLIBC. The gdc-client tool I downloaded through R seemed to be for Ubuntu and not CentOS, though I did it on CentOS 7. I then downloaded the gdc-client for CentOS and it worked fine.

Discussions
linux - How to upgrade glibc from version 2.12 to 2.14 on CentOS? - Stack Overflow
I do not know how to upgrade glibc from version 2.12 to 2.14 on CentOS 6.3. I need your help. ... You cannot update glibc on Centos 6 safely. However you can install 2.14 alongside 2.12 easily, then use it to compile projects etc. More on stackoverflow.com
🌐 stackoverflow.com
package management - Cannot update glibc on CentOS 7 - Unix & Linux Stack Exchange
I have CentOS 7 installed. I want to install the APR package for Apache, and I'm told I cannot install it because it requires at least glibc.2.14 while I have glibc.2.12 installed. I have downloade... More on unix.stackexchange.com
🌐 unix.stackexchange.com
centos7 - Upgrade glibc 2.17 to 2.19+ on CentOS 7 - Stack Overflow
First of all, Dropbox emailed me saying that I must upgrade glibc to 2.19+, otherwise Dropbox will not run.Then I follow the steps below to upgrade glibc. More on stackoverflow.com
🌐 stackoverflow.com
upgrade - How to update glibc to 2.14 in CentOS 6.5 - Unix & Linux Stack Exchange
I want to install Android NDK on my CentOS 6.5 machine. But when I ran the program, it says it needs glibc 2.14 to be able to run. My CentOS 6.5 only has Glibc 2.12 installed. So I tried to update ... More on unix.stackexchange.com
🌐 unix.stackexchange.com
December 29, 2014
🌐
GitHub
gist.github.com › harv › f86690fcad94f655906ee9e37c85b174
update glibc to 2.17 for CentOS 6 · GitHub
update glibc to 2.17 for CentOS 6. GitHub Gist: instantly share code, notes, and snippets.
🌐
Stack Overflow
stackoverflow.com › questions › 35616650 › how-to-upgrade-glibc-from-version-2-12-to-2-14-on-centos
linux - How to upgrade glibc from version 2.12 to 2.14 on CentOS? - Stack Overflow
Top answer
1 of 4
91

You cannot update glibc on Centos 6 safely. However you can install 2.14 alongside 2.12 easily, then use it to compile projects etc. Here is how:

mkdir ~/glibc_install; cd ~/glibc_install
wget http://ftp.gnu.org/gnu/glibc/glibc-2.14.tar.gz
tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
sudo make install
export LD_LIBRARY_PATH=/opt/glibc-2.14/lib
2 of 4
14

I found this source very useful and doesn't has much SEO. It lists the most common errors you might encounter while using @UnitasBrooks great answer and I'm afraid it gets lost in the future.

This is the link to the original post

I will copy, paste it here (I faced the last problem and it fixed it, however I didn't try all the problems/solutions listed and you try it on your own risk)

Glibc installation

The GNU C Library, commonly known as glibc, is the GNU Project's implementation of the C standard library. My environment required glibc (version 2.14) and it took a bit of fiddling to get it to work, so hopefully this will save you some time.

0.Glibc Installation Dependencies

Bash: sh
Binutils: ar, as, ld, ranlib, readelf
Diffutils: cmp
Fileutils: chmod, cp, install, ln, mknod, mv, mkdir, rm, touch
Gcc: cc, cc1, collect2, cpp, gcc
Grep: egrep, grep
Gzip: gzip
Make: make
Gawk: gawk
Sed: sed
Sh-utils: date, expr, hostname, pwd, uname
Texinfo: install-info, makeinfo
Textutils: cat, cut, sort, tr

1.Download installation package

http://www.gnu.org/software/libc/ for all versions.
http://ftp.gnu.org/gnu/glibc/glibc-2.14.tar.gz for version 2.14.

2.Compile and install

To avoid disturb current environment, compile and install this version separately by configuring prefix.

[root@localhost ~]# tar xvf glibc-2.14.tar.gz
[root@localhost ~]# cd glibc-2.14
[root@localhost glibc-2.14]# mkdir build
[root@localhost glibc-2.14]# cd ./build
[root@localhost build]# ../configure --prefix=/opt/glibc-2.14
[root@localhost build]# make -j4
[root@localhost build]# make install
[root@localhost build]# export LD_LIBRARY_PATH=/opt/glibc-2.14/lib:$LD_LIBRARY_PATH

3.To check glibc versions installed

root@localhost:~/intel64/runtime/glibc$ strings libc.so.6 | grep GLIBC
GLIBC_2.2.5
GLIBC_2.2.6
GLIBC_2.3
GLIBC_2.3.2
GLIBC_2.3.3
GLIBC_2.3.4
GLIBC_PRIVATE

4.Compiling errors

Error:

make[1]: *** No rule to make target /mnt/lfs/sourcenew/glibc-build/Versions.all', needed by/mnt/lfs/sourcenew/glibc-build/abi-versions.h'. Stop.

Solution:

sudo apt-get install gawk
sudo apt-get install texinfo

Error:

make[2]: *** [/mnt/lfs/sources/glibc-build/misc/syslog.o] Error 1

Solution:

make clean
make -j2 CFLAGS="-U_FORTIFY_SOURCE -O2 -fno-stack-protector"

Error:

/Downloads/glibc-2.14/build/elf/ldconfig: Can't open configuration file /opt/glibc-2.14/etc/ld.so.conf: No such file or directory

Solution:

:/opt/glibc-2.14/etc$ sudo sh -c "echo '/usr/local/lib' >> ld.so.conf" 
:/opt/glibc-2.14/etc$ sudo sh -c "echo '/opt/lib' >> ld.so.conf"
🌐
GitHub
gist.github.com › carlesloriente › ab3387e7d035ed400dc2816873e9089e
Compile and install GLIBC 2.18 in CentOS 7 · GitHub
the source url is ineffective, replace it with https://ftp.gnu.org/gnu/glibc/glibc-2.18.tar.gz · Copy link · Can I update it without root? Copy link · ubuntu20.4如何将glibc2.31升级到2.32？ · Brooooooklyn/canvas#370 · It is more straightforward to replace centos7 (after all, centos7 is really old) Copy link ·
🌐
Stack Exchange
unix.stackexchange.com › questions › 176608 › cannot-update-glibc-on-centos-7
package management - Cannot update glibc on CentOS 7 - Unix & Linux Stack Exchange
Top answer
1 of 2
4

You need to download the following 4 packages from a mirror:

  1. glibc-2.17-55.el7.i686.rpm
  2. glibc-2.17-55.el7.x86_64.rpm
  3. glibc-common-2.17-55.el7.x86_64.rpm
  4. glibc-headers-2.17-55.el7.x86_64.rpm

After doing so, issue a rpm -ivh glibc-*. If that fails, download:

  1. glibc-devel-2.17-55.el7.i686.rpm
  2. glibc-devel-2.17-55.el7.x86_64.rpm

and reissue the command again. After getting glibc updated, issue a yum update to resolve any new dependencies.

2 of 2
1

If you have glibc 2.12 installed, you do NOT have CentOS7; you're on CentOS6. While there's been a lot of grief about the locking of major/minor versions after distro release - it's for stability, testing and certification; you'll learn the value later - the version you're looking at should not exist under an up-to-date centos7.

Update your CentOS7, do a yum install of apr (apr-devel too?) and you're done.

If you DO have CentOS6, apr-1.3.9-5.el6_2.x86_64 requires glibc-2.12 . Yum install will get you what you need here, as well.

In general

  1. Don't mix RPMs from alient repositories: you're looking for pain.
  2. Don't mix RPMs from two different distro releases -- they're designed to work together, and tested so.
  3. if it's suddenly hard, or there are strange messages, there's a really good chance you're doing something you should not.
  4. Dependency Hell [tm] is self-inflicted. No exceptions.

I worked at a distro; not in Support but adjacent to it. #4 is a well-tested theory.

🌐
Stack Overflow
stackoverflow.com › questions › 52966497 › upgrade-glibc-2-17-to-2-19-on-centos-7
centos7 - Upgrade glibc 2.17 to 2.19+ on CentOS 7 - Stack Overflow
Top answer
1 of 1
4

Take a look at this thread. There is a workaround for this problem, basically by cheating Dropbox to think that the glibc version is 2.19, when it is actually 2.17:

Create dropboxcheat.c with this code:

const char *gnu_get_libc_version (void) {
        return "2.19"; }

compile the cheat .so

gcc -Wall -fPIC -shared -o dropboxcheat.so dropboxcheat.c

move the .so to /usr/local/lib64/ add this line in dropbox.py, right before subprocess.Popen....., in function start_dropbox

os.environ['LD_PRELOAD'] = "/usr/local/lib64/dropboxcheat.so"

Run dropbox normally and it should ask to relogin.

Credit to Pablo for this solution.

I haven't tried it myself yet, but plan on doing so early next week. Let me know if this works out.

🌐
Stack Exchange
unix.stackexchange.com › questions › 176489 › how-to-update-glibc-to-2-14-in-centos-6-5
upgrade - How to update glibc to 2.14 in CentOS 6.5 - Unix & Linux Stack Exchange
Top answer
1 of 3
92

You cannot update glibc on Centos 6 safely. However you can install 2.14 alongside 2.12 easily, then use it to compile projects etc. Here is how:

mkdir ~/glibc_install; cd ~/glibc_install 

wget http://ftp.gnu.org/gnu/glibc/glibc-2.14.tar.gz

tar zxvf glibc-2.14.tar.gz

cd glibc-2.14

mkdir build

cd build

../configure --prefix=/opt/glibc-2.14

make -j4

sudo make install

export LD_LIBRARY_PATH="/opt/glibc-2.14/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
2 of 3
9

To install glibc 2.14 in parallel, add the configure prefix:

tar zxvf glibc-2.14.tar.gz
cd glibc-2.14
mkdir build
cd build
../configure --prefix=/opt/glibc-2.14
make -j4
make install

Following this process, you'll be able to build 2.14 but you will need to tell the compiler where to look for glibc.

Below are the ways you can expose the glibc to your program.

  1. LD_LIBRARY_PATH=/opt/glibc-2.14/lib

    export LD_LIBRARY_PATH.

    The library is exposed during your current login session.

  2. You can permanently link your new glibc version like so, but please read the WARNING below:

    ln -sf /opt/glibc-2.14/glibc-2.14.so /lib/libc.so.6.

Since libc.so.6 is just a symbolic link. Executing the above command will make the link point towards the new glibc library. However this step is not recommended since there are many programs in Linux which depend on older versions and will stop working.

Find elsewhere
🌐
Itayemi
itayemi.com › blog › 2023 › 03 › 01 › upgrading-rhel-centos-v-7-x-to-glibc-version-2-20
Upgrading RHEL/CentOS v 7.x to GLIBC version 2.20 | Illumination
Download the glibc-2.x source RPM and rebuild it: [root@rhel77c ~]# wget ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/21/SRPMS/g/glibc-2.20-8.fc21.src.rpm [root@rhel77c ~]# rpmbuild –rebuild glibc-2.20-8.fc21.src.rpm
🌐
UMA Technology
umatechnology.org › home › how to update the glibc (gnu libc) in centos / red hat
How to Update the glibc (GNU libc) in CentOS / Red Hat - UMA Technology
December 18, 2024 - In this article, we will discuss the importance of updating the glibc, the steps to update it in CentOS and Red Hat systems, and best practices for managing glibc updates.
🌐
Serverkurma
serverkurma.com › linux › how-to-update-glibc-newer-version-on-centos-6-x
How to Update glibc Newer Version on Centos 6.x – ServerKurma – Bilişim Hizmetleri
February 6, 2018 - We can get soruce file in 2 ways, using git or ftp. You can get latest version from git. We need GLIBC_2.17 version for our centos 6.x so we will use ftp.
🌐
Devtuts
devtuts.net › en › linux › how-to-update-glibc.html
How to update glibc
June 15, 2024 - Most distributions ship tested glibc updates via their package manager: ... # Debian / Ubuntu / Kali sudo apt-get update && sudo apt-get install --reinstall libc6 # RHEL / CentOS / Rocky / AlmaLinux sudo yum reinstall glibc # or: sudo dnf reinstall glibc # openSUSE / SLES sudo zypper in --force ...
🌐
Caoyu
blog.caoyu.info › centos7-upgrade-libc.html
How to upgrade glibc on CentOS 7 | 我还是个宝宝!
August 18, 2024 - Upgrade glibc from 2.17 to 2.31 on CentOS 7
🌐
Reddit
reddit.com › r/centos › centos 7, yum update error with glibc-devel
r/CentOS on Reddit: centos 7, yum update error with glibc-devel
September 17, 2023 -

I am getting an error on CentOS 7 when trying to perform a yum update.

It's a small LAMP server. apache, php 7, mariadb.

When I run yum update, I get the following error that I am hoping someone can help resolve. 

Error: Package: glibc-devel-2.17-324.el7_9.x86_64 (@updates)
           Requires: glibc-headers = 2.17-324.el7_9
           Removing: glibc-headers-2.17-324.el7_9.x86_64 (@updates)
               glibc-headers = 2.17-324.el7_9
           Updated By: glibc-headers-2.17-326.el7_9.x86_64 (updates)
               glibc-headers = 2.17-326.el7_9
           Available: glibc-headers-2.17-317.el7.x86_64 (base)
               glibc-headers = 2.17-317.el7
           Available: glibc-headers-2.17-322.el7_9.x86_64 (updates)
               glibc-headers = 2.17-322.el7_9
           Available: glibc-headers-2.17-323.el7_9.x86_64 (updates)
               glibc-headers = 2.17-323.el7_9
           Available: glibc-headers-2.17-325.el7_9.x86_64 (updates)
               glibc-headers = 2.17-325.el7_9

cat /etc/*elease
CentOS Linux release 7.9.2009 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
CPE_NAME="cpe:/o:centos:centos:7"
CentOS Linux release 7.9.2009 (Core)

[root@www scripts]# sudo yum -y update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.xenyth.net
 * elrepo: linux-mirrors.fnal.gov
 * epel: mirror.dst.ca
 * extras: mirror.xenyth.net
 * remi-safe: cdn.centos.no
 * updates: mirror.xenyth.net
Resolving Dependencies
--> Running transaction check
---> Package apr-util.x86_64 0:1.5.2-6.el7 will be updated
---> Package apr-util.x86_64 0:1.5.2-6.el7_9.1 will be an update
---> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.9 will be updated
---> Package bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.14 will be an update
---> Package ca-certificates.noarch 0:2020.2.41-70.0.el7_8 will be updated
---> Package ca-certificates.noarch 0:2022.2.54-74.el7_9 will be an update
---> Package cronie.x86_64 0:1.4.11-23.el7 will be updated
---> Package cronie.x86_64 0:1.4.11-24.el7_9 will be updated
---> Package cronie.x86_64 0:1.4.11-25.el7_9 will be an update
---> Package cronie-anacron.x86_64 0:1.4.11-24.el7_9 will be updated
---> Package cronie-anacron.x86_64 0:1.4.11-25.el7_9 will be an update
---> Package diffutils.x86_64 0:3.3-5.el7 will be updated
---> Package diffutils.x86_64 0:3.3-6.el7_9 will be an update
---> Package elrepo-release.noarch 0:7.0-5.el7.elrepo will be updated
---> Package elrepo-release.noarch 0:7.0-6.el7.elrepo will be an update
---> Package expat.x86_64 0:2.1.0-14.el7_9 will be updated
---> Package expat.x86_64 0:2.1.0-15.el7_9 will be an update
---> Package glibc-headers.x86_64 0:2.17-324.el7_9 will be updated
--> Processing Dependency: glibc-headers = 2.17-324.el7_9 for package: glibc-devel-2.17-324.el7_9.x86_64
---> Package glibc-headers.x86_64 0:2.17-326.el7_9 will be an update
---> Package grub2.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-common.noarch 1:2.02-0.87.el7.9 will be updated
---> Package grub2-common.noarch 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-pc.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2-pc.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-pc-modules.noarch 1:2.02-0.87.el7.9 will be updated
---> Package grub2-pc-modules.noarch 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-tools.x86_64 1:2.02-0.87.el7.centos.6 will be updated
---> Package grub2-tools.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-tools-extra.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2-tools-extra.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package grub2-tools-minimal.x86_64 1:2.02-0.87.el7.9 will be updated
---> Package grub2-tools-minimal.x86_64 1:2.02-0.87.0.2.el7.centos.11 will be an update
---> Package httpd.x86_64 0:2.4.6-97.el7.centos will be updated
---> Package httpd.x86_64 0:2.4.6-99.el7.centos.1 will be an update
---> Package httpd-tools.x86_64 0:2.4.6-97.el7.centos.5 will be updated
---> Package httpd-tools.x86_64 0:2.4.6-99.el7.centos.1 will be an update
---> Package kernel.x86_64 0:3.10.0-1160.95.1.el7 will be installed
---> Package kernel-headers.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package kernel-headers.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package kernel-tools.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package kernel-tools.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package kernel-tools-libs.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package kernel-tools-libs.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package kmod-ixgbe.x86_64 0:5.8.1-1.el7_9.elrepo will be updated
---> Package kmod-ixgbe.x86_64 0:5.8.1-2.el7_9.elrepo will be updated
---> Package kmod-ixgbe.x86_64 0:5.12.5-1.el7_9.elrepo will be updated
---> Package kmod-ixgbe.x86_64 0:5.12.5-2.el7_9.elrepo will be an update
---> Package kpartx.x86_64 0:0.4.9-135.el7_9 will be updated
---> Package kpartx.x86_64 0:0.4.9-136.el7_9 will be an update
---> Package krb5-devel.x86_64 0:1.15.1-51.el7_9 will be updated
---> Package krb5-devel.x86_64 0:1.15.1-55.el7_9 will be an update
---> Package krb5-libs.x86_64 0:1.15.1-51.el7_9 will be updated
---> Package krb5-libs.x86_64 0:1.15.1-55.el7_9 will be an update
---> Package libXpm.x86_64 0:3.5.12-1.el7 will be updated
---> Package libXpm.x86_64 0:3.5.12-2.el7_9 will be an update
---> Package libkadm5.x86_64 0:1.15.1-51.el7_9 will be updated
---> Package libkadm5.x86_64 0:1.15.1-55.el7_9 will be an update
---> Package microcode_ctl.x86_64 2:2.1-73.11.el7_9 will be updated
---> Package microcode_ctl.x86_64 2:2.1-73.13.el7_9 will be updated
---> Package microcode_ctl.x86_64 2:2.1-73.16.el7_9 will be an update
---> Package mod_ssl.x86_64 1:2.4.6-97.el7.centos.5 will be updated
---> Package mod_ssl.x86_64 1:2.4.6-99.el7.centos.1 will be an update
---> Package nspr.x86_64 0:4.32.0-1.el7_9 will be updated
---> Package nspr.x86_64 0:4.34.0-3.1.el7_9 will be an update
---> Package nss.x86_64 0:3.67.0-4.el7_9 will be updated
---> Package nss.x86_64 0:3.79.0-5.el7_9 will be an update
---> Package nss-pem.x86_64 0:1.0.3-7.el7 will be updated
---> Package nss-pem.x86_64 0:1.0.3-7.el7_9.1 will be an update
---> Package nss-softokn.x86_64 0:3.67.0-3.el7_9 will be updated
---> Package nss-softokn.x86_64 0:3.79.0-4.el7_9 will be an update
---> Package nss-softokn-freebl.x86_64 0:3.67.0-3.el7_9 will be updated
---> Package nss-softokn-freebl.x86_64 0:3.79.0-4.el7_9 will be an update
---> Package nss-sysinit.x86_64 0:3.67.0-4.el7_9 will be updated
---> Package nss-sysinit.x86_64 0:3.79.0-5.el7_9 will be an update
---> Package nss-tools.x86_64 0:3.67.0-4.el7_9 will be updated
---> Package nss-tools.x86_64 0:3.79.0-5.el7_9 will be an update
---> Package nss-util.x86_64 0:3.67.0-1.el7_9 will be updated
---> Package nss-util.x86_64 0:3.79.0-1.el7_9 will be an update
---> Package openssh.x86_64 0:7.4p1-21.el7 will be updated
---> Package openssh.x86_64 0:7.4p1-23.el7_9 will be an update
---> Package openssh-clients.x86_64 0:7.4p1-22.el7_9 will be updated
---> Package openssh-clients.x86_64 0:7.4p1-23.el7_9 will be an update
---> Package openssh-server.x86_64 0:7.4p1-21.el7 will be updated
---> Package openssh-server.x86_64 0:7.4p1-23.el7_9 will be an update
---> Package openssl.x86_64 1:1.0.2k-25.el7_9 will be updated
---> Package openssl.x86_64 1:1.0.2k-26.el7_9 will be an update
---> Package openssl-devel.x86_64 1:1.0.2k-25.el7_9 will be updated
---> Package openssl-devel.x86_64 1:1.0.2k-26.el7_9 will be an update
---> Package openssl-libs.x86_64 1:1.0.2k-25.el7_9 will be updated
---> Package openssl-libs.x86_64 1:1.0.2k-26.el7_9 will be an update
---> Package polkit.x86_64 0:0.112-26.el7 will be updated
---> Package polkit.x86_64 0:0.112-26.el7_9.1 will be an update
---> Package python.x86_64 0:2.7.5-90.el7 will be updated
---> Package python.x86_64 0:2.7.5-93.el7_9 will be an update
---> Package python-libs.x86_64 0:2.7.5-90.el7 will be updated
---> Package python-libs.x86_64 0:2.7.5-93.el7_9 will be an update
---> Package python-perf.x86_64 0:3.10.0-1160.66.1.el7 will be updated
---> Package python-perf.x86_64 0:3.10.0-1160.95.1.el7 will be an update
---> Package remi-release.noarch 0:7.9-3.el7.remi will be updated
---> Package remi-release.noarch 0:7.9-5.el7.remi will be an update
---> Package rsync.x86_64 0:3.1.2-10.el7 will be updated
---> Package rsync.x86_64 0:3.1.2-12.el7_9 will be an update
---> Package rsyslog.x86_64 0:8.24.0-57.el7_9.1 will be updated
---> Package rsyslog.x86_64 0:8.24.0-57.el7_9.2 will be updated
---> Package rsyslog.x86_64 0:8.24.0-57.el7_9.3 will be an update
---> Package s3cmd.noarch 0:2.2.0-1.el7 will be updated
---> Package s3cmd.noarch 0:2.3.0-4.el7 will be an update
---> Package sudo.x86_64 0:1.8.23-10.el7_9.2 will be updated
---> Package sudo.x86_64 0:1.8.23-10.el7_9.3 will be an update
---> Package systemd.x86_64 0:219-78.el7_9.3 will be updated
---> Package systemd.x86_64 0:219-78.el7_9.7 will be an update
---> Package systemd-libs.x86_64 0:219-78.el7_9.5 will be updated
---> Package systemd-libs.x86_64 0:219-78.el7_9.7 will be an update
---> Package systemd-sysv.x86_64 0:219-78.el7_9.5 will be updated
---> Package systemd-sysv.x86_64 0:219-78.el7_9.7 will be an update
---> Package tuned.noarch 0:2.11.0-11.el7_9 will be updated
---> Package tuned.noarch 0:2.11.0-12.el7_9 will be an update
---> Package tzdata.noarch 0:2022a-1.el7 will be updated
---> Package tzdata.noarch 0:2023c-1.el7 will be an update
---> Package xz.x86_64 0:5.2.2-1.el7 will be updated
---> Package xz.x86_64 0:5.2.2-2.el7_9 will be an update
---> Package xz-devel.x86_64 0:5.2.2-1.el7 will be updated
---> Package xz-devel.x86_64 0:5.2.2-2.el7_9 will be an update
---> Package xz-libs.x86_64 0:5.2.2-1.el7 will be updated
---> Package xz-libs.x86_64 0:5.2.2-2.el7_9 will be an update
---> Package zlib.x86_64 0:1.2.7-20.el7_9 will be updated
---> Package zlib.x86_64 0:1.2.7-21.el7_9 will be an update
---> Package zlib-devel.x86_64 0:1.2.7-20.el7_9 will be updated
---> Package zlib-devel.x86_64 0:1.2.7-21.el7_9 will be an update
--> Finished Dependency Resolution
--> Running transaction check
---> Package glibc-headers.x86_64 0:2.17-324.el7_9 will be updated
--> Processing Dependency: glibc-headers = 2.17-324.el7_9 for package: glibc-devel-2.17-324.el7_9.x86_64
---> Package kernel.x86_64 0:3.10.0-1160.el7 will be erased
--> Finished Dependency Resolution

Error: Package: glibc-devel-2.17-324.el7_9.x86_64 (@updates)
           Requires: glibc-headers = 2.17-324.el7_9
           Removing: glibc-headers-2.17-324.el7_9.x86_64 (@updates)
               glibc-headers = 2.17-324.el7_9
           Updated By: glibc-headers-2.17-326.el7_9.x86_64 (updates)
               glibc-headers = 2.17-326.el7_9
           Available: glibc-headers-2.17-317.el7.x86_64 (base)
               glibc-headers = 2.17-317.el7
           Available: glibc-headers-2.17-322.el7_9.x86_64 (updates)
               glibc-headers = 2.17-322.el7_9
           Available: glibc-headers-2.17-323.el7_9.x86_64 (updates)
               glibc-headers = 2.17-323.el7_9
           Available: glibc-headers-2.17-325.el7_9.x86_64 (updates)
               glibc-headers = 2.17-325.el7_9

 You could try using --skip-broken to work around the problem
** Found 23 pre-existing rpmdb problem(s), 'yum check' output follows:
binutils-2.27-44.base.el7_9.1.x86_64 is a duplicate with binutils-2.27-44.base.el7.x86_64
cronie-1.4.11-24.el7_9.x86_64 is a duplicate with cronie-1.4.11-23.el7.x86_64
glibc-devel-2.17-324.el7_9.x86_64 has missing requires of glibc = ('0', '2.17', '324.el7_9')
glibc-devel-2.17-325.el7_9.x86_64 is a duplicate with glibc-devel-2.17-324.el7_9.x86_64
glibc-devel-2.17-325.el7_9.x86_64 has missing requires of glibc = ('0', '2.17', '325.el7_9')
glibc-devel-2.17-325.el7_9.x86_64 has missing requires of glibc-headers = ('0', '2.17', '325.el7_9')
glibc-devel-2.17-326.el7_9.x86_64 is a duplicate with glibc-devel-2.17-325.el7_9.x86_64
glibc-devel-2.17-326.el7_9.x86_64 has missing requires of glibc-headers = ('0', '2.17', '326.el7_9')
glibc-headers-2.17-324.el7_9.x86_64 has missing requires of glibc = ('0', '2.17', '324.el7_9')
1:grub2-pc-2.02-0.87.el7.9.x86_64 has missing requires of grub2-tools = ('1', '2.02', '0.87.el7.9')
1:grub2-tools-2.02-0.87.el7.centos.6.x86_64 has missing requires of grub2-common = ('1', '2.02', '0.87.el7.centos.6')
1:grub2-tools-2.02-0.87.el7.centos.6.x86_64 has missing requires of grub2-tools-minimal = ('1', '2.02', '0.87.el7.centos.6')
1:grub2-tools-extra-2.02-0.87.el7.9.x86_64 has missing requires of grub2-tools = ('1', '2.02', '0.87.el7.9')
gzip-1.5-11.el7_9.x86_64 is a duplicate with gzip-1.5-10.el7.x86_64
httpd-2.4.6-97.el7.centos.x86_64 has missing requires of httpd-tools = ('0', '2.4.6', '97.el7.centos')
kmod-ixgbe-5.8.1-2.el7_9.elrepo.x86_64 is a duplicate with kmod-ixgbe-5.8.1-1.el7_9.elrepo.x86_64
kmod-ixgbe-5.12.5-1.el7_9.elrepo.x86_64 is a duplicate with kmod-ixgbe-5.8.1-2.el7_9.elrepo.x86_64
2:microcode_ctl-2.1-73.13.el7_9.x86_64 is a duplicate with 2:microcode_ctl-2.1-73.11.el7_9.x86_64
1:mod_ssl-2.4.6-97.el7.centos.5.x86_64 has missing requires of httpd = ('0', '2.4.6', '97.el7.centos.5')
openssh-clients-7.4p1-22.el7_9.x86_64 has missing requires of openssh = ('0', '7.4p1', '22.el7_9')
rsyslog-8.24.0-57.el7_9.2.x86_64 is a duplicate with rsyslog-8.24.0-57.el7_9.1.x86_64
systemd-219-78.el7_9.3.x86_64 has missing requires of systemd-libs = ('0', '219', '78.el7_9.3')
systemd-sysv-219-78.el7_9.5.x86_64 has missing requires of systemd = ('0', '219', '78.el7_9.5')
Top answer
1 of 1
3
You have a failed yum transaction, which is why you have the list of problems at the bottom. Try running yum-complete-transaction to complete it. If that doesn’t work, you’ll need to use package-cleanup --cleandupes to remove the duplicate packages.
🌐
Stack Overflow
stackoverflow.com › questions › 60561735 › how-to-upgrade-glibc-from-version-2-12-to-2-15-on-centos6
linux - How to upgrade glibc from version 2.12 to 2.15 on CentOS6? - Stack Overflow
Top answer
1 of 1
2

On CentOS, you can only upgrade glibc by upgrading to a newer CentOS version. Core system libraries are an integral part of the operating system, and if you replace them, you have a different operating system. At that point, you might as well just upgrade.

To solve your original problem, you need to use a build of Tensorflow for Red Hat Enterprise Linux 6 or CentOS 6.

For future reference, it would be interesting to know why you are using an operating system that was released nearly ten years ago for a compute-intense task (like most tasks involving Tensorflow are). If this is original hardware from 2010 or earlier, it is not very efficient. If the hardware has been upgraded since, why not the operating system as well? Typically, hardware replacement is an opportunity for migrating to a new operating system, too.

🌐
Xwebhosting
halo.xwebhosting.org › knowledgebase › 87 › How-to-Update-the-glibc-GNU-libc-in-CentOS-or-Red-Hat.html
How to Update the glibc (GNU libc) in CentOS / Red Hat - Knowledgebase - XWEBHosting, LLC
In this case, yum is the rpm-based package manager for both Red Hat and CentOS, -y, –assumeyes gives yes as an answer to any question which would be asked by running the command, update is for updating the package, and glibcis the package you’re updating!
🌐
Ngelinux
ngelinux.com › home › how to install glibc package version 2.28+ on rhel 7 unofficially for testing purposes?
How to install glibc package version 2.28+ on RHEL 7 unofficially for testing purposes? | New Generation Enterprise Linux
June 22, 2022 - [root@ngelinux001 eag]# rpm -ivh ./glibc-langpack-sw-2.28-199.el8.x86_64.rpm --nodeps warning: ./glibc-langpack-sw-2.28-199.el8.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 8483c65d: NOKEY Preparing... ################################# [100%] Updating / installing...
🌐
Stack Overflow
stackoverflow.com › questions › 68694993 › building-and-using-a-newer-glibc-on-centos-7
linux - Building and using a newer GLIBC on CentOS 7 - Stack Overflow
Top answer
1 of 1
3

Try ./testrun.sh /bin/ls.

That said, you will really be better off building the Python package for your system, instead of trying to make non-system GLIBC, as Danila Vershinin suggested.

Update:

libselinux.so.1: ...: No such file or directory

The testrun.sh for the new GLIBC does not look in system directories (e.g. /usr/lib64). You need to append system directories to the --library-path it uses. E.g. change

--library-path "${builddir}":"${builddir}"/math:"${builddir}"/elf:"${builddir}"/dlfcn:"${builddir}"/nss:"${builddir}"/nis:"${builddir}"/rt:"${builddir}"/resolv:"${builddir}"/mathvec:"${builddir}"/support:"${builddir}"/crypt:"${builddir}"/nptl

to:

--library-path "${builddir}":"${builddir}"/math:"${builddir}"/elf:"${builddir}"/dlfcn:"${builddir}"/nss:"${builddir}"/nis:"${builddir}"/rt:"${builddir}"/resolv:"${builddir}"/mathvec:"${builddir}"/support:"${builddir}"/crypt:"${builddir}"/nptl:/usr/lib64:/lib64

(or something like that).

🌐
GitHub
gist.github.com › latuminggi › 5da516b85dc4b1d944a00dc8dbca8daf
Updating glibc, libstdc++, and gcc on RHEL / CentOS 6 · GitHub
Updating glibc, libstdc++, and gcc on RHEL / CentOS 6 - Updating glibc, libstdc++, and gcc on RHEL (CentOS) 6
🌐
Stack Exchange
unix.stackexchange.com › questions › 510154 › unable-to-update-glibc-to-the-latest-version
centos - Unable to update glibc to the latest version - Unix & Linux Stack Exchange
Top answer
1 of 1
3

Your last comment reveals your issue.

Remove the exclude line from the repo file and/or /etc/yum.conf, run yum clean all, and try to install glibc again. That line is excluding the package(s) that you need to update.

Related queries
install glibc centos 7
install glibc-2.28 centos 7
centos 7 glibc version
install glibc 2.27 on centos 7
install glibc 2.18 centos 7
glibc 2.18 centos 7
update glibc centos 7
upgrade glibc redhat