RHEL 6 - how to install 'GLIBC_2.14' or 'GLIBC_2.15'?

Asked 31/8, 2015 at 17:29 Answered 25/1, 2018 at 12:59

I need these 2 packages installed on RHEL 6 linux system. They are required by several other programs.

When I do:

sudo yum install glibc-devel

this is output:

Loaded plugins: product-id, security
Setting up Install Process
Package glibc-devel-2.12-1.166.el6_7.1.x86_64 already installed and latest version
Nothing to do

Is there some EPEL with GLIBC_2.15 for RHEL? If not - what is a workaround here?

Repp answered 31/8, 2015 at 17:29 Comment(16)

What needs those? What error are you seeing? What are you doing when you get that error? – Model 31/8, 2015 at 18:8

Any program that needs these library show error. Here is one example: $ lzturbo lzturbo: /lib64/libm.so.6: version GLIBC_2.15' not found (required by lzturbo) lzturbo: /lib64/libc.so.6: version GLIBC_2.14' not found (required by lzturbo) – Repp 31/8, 2015 at 18:31

Where did you get lzturbo from? No official RHEL 6 software should have this problem. Neither should anything you built on RHEL 6 from source. So where did this "random" binary come from? And why did you install it? – Model 31/8, 2015 at 18:34

It came as a download binary. It came from company download site. Does this mean that no experimental software can run on RHEL without having a 'official bless' from RHEL? That is insane.. What if you want to make new discoveries with different software? Do you need to wait for RHEL? Anyway let's focus on a main question: How do you install / point GLIBC_2.15 on RHEL? If you think this discussion about official/non-official RHEL software will help me somehow - please continue in that direction. If not - please provide ideas/solution if you have. thanks – Repp 31/8, 2015 at 18:47

I'm suggesting you don't install that because it is too new. It depends on versions of software that RHEL 6 does not contain. And yes if you want support from RHEL I believe you do need to wait for them to package the software. I imagine if you ask them for support for something you installed externally they will tell you they won't support it and to do ask the vendor of that software. (Which isn't to say it doesn't work just that when it breaks you get to keep both pieces.) The vendor gave you software that wiil not work on RHEL 6 as built. Go ask them for a RHEL 6 compatible version. – Model 31/8, 2015 at 18:55

This approach will take weeks easily (to ask RHEL for support). All I want is to run the software (no need to be installed). Want to test it - close it. No need to be install, run for long time etc. Also tried same software on AWS Centos and is working there without any installation. That means problem is only with GLIBC_2.15 (lack of ability to update that library). Do you know how to update / point to GLIBC_2.15 ? – Repp 31/8, 2015 at 19:52

You misunderstood me. I didn't tell you to ask for support. I said you probably won't be able to get any if you need it later. AWS is not stock CentOS they modify all sorts of things. RHEL/CentOS 6 does not have a glibc version with those symbols. You cannot get them without building your own glibc package/etc. If you want to use RHEL/CentOS 6 for this software you need a version of the software from the vendor that is built to work on RHEL/CentOS 6 and not built for some other (newer) system. – Model 31/8, 2015 at 20:4

Ok. No need support later on. Is it too complicated to configure a system similar like AWS did (for parts that is needed for this library)? What they did in a 'black box' so that this software can work on their CentOS but not on stock RHEL one? – Repp 31/8, 2015 at 20:27

They repackaged huge parts of the OS. If you want to do that you can but then you don't have RHEL anymore. You have JoeOS (or whatever). Feel free to do that if you want but it isn't a simple process. – Model 1/9, 2015 at 1:20

Great. I am stucked now.. – Repp 1/9, 2015 at 5:0

Go see if the vendor has a version of the binary intended for use on RHEL/CentOS 6. If they do, use that. If not, try using RHEL/CentOS 7 or some other more up to date system then RHEL/CentOS 6. – Model 1/9, 2015 at 13:9

I have: Red Hat Enterprise Linux Workstation release 6.7 (Santiago) Is that RHEL recommended anyway or should I go for a newer version regardless of this problem with GLIBC? – Repp 1/9, 2015 at 15:1

That's the newest release of RHEL 6 as far as I know. RHEL 6 will never get a new enough glibc for what you want here. That's not how RHEL versioning works. If you want a newer glibc version you get to use RHEL 7 or some other distribution. – Model 1/9, 2015 at 15:3

Which link should I believe about what GLIBC have specific version of RHEL?: 1) access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/… 2) distrowatch.com/table.php?distribution=redhat – Repp 1/9, 2015 at 15:9

For RHEL 6 they agree so pick whichever you want to believe.. I'm not sure why the RH docs appear to be wrong about what RHEL 7 contains though. – Model 1/9, 2015 at 16:14

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? – Repp 1/9, 2015 at 21:31

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.

Aziza answered 12/12, 2016 at 19:2 Comment(7)

I used glibc-2.15. Therefore I had to do touch /opt/glibc-2.15/etc/ld.so.conf because otherwise make install would fail. – Manasseh 22/10, 2017 at 22:37

Did not work in RHEL 6.5 , Gives Segementation Fault for me too. – Aphis 3/8, 2018 at 1:8

@Aphis in which of these installation steps, did you get the segmentation fault error? – Aziza 10/9, 2018 at 13:23

I did this, but the program I am trying to install still complains about not finding lib.so.6 (GLIBC_2.14)(64 bit)....aniy ideas? – Blowpipe 4/2, 2019 at 22:31

Step 6: works better with sudo make rather than just make. – Decasyllable 4/9, 2019 at 16:28

Great. Afters hours of struggling on other sites, I found your answer which resolved my issue. Thanks..! – Submarginal 21/10, 2019 at 11:59

Segmentation faults you're facing because of that other binutils still depend on old libc, however since you're changing LD_LIBRARY_PATH now they're using new version which yields segmentation fault. Even basic commands like ls/cd fails. – Mayst 2/9, 2020 at 8:42

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.

Garlan answered 2/9, 2015 at 6:4 Comment(4)

Given that this appears to be a vendor distributed binary that makes the simple "recompile it" option unavailable (that would avoid this problem entirely in the first place most likely) which just leaves the chroot (effectively an entirely different system) or the binary editing of requirements (assuming your list was exhaustive). – Model 2/9, 2015 at 13:41

Sorry I did not understand what are you saying.. What is chroot and how do you do binary editing? – Repp 3/9, 2015 at 3:30

@Repp Did you read the linked answer? The solution is quite non-trivial, and if you can't be bothered to find out (by googling) what is chroot and how to do binary editing, then I am afraid your problem can't be solved by you. – Garlan 3/9, 2015 at 3:50

Yeah.. I am still beginner for those custom things. I know some stuff in Linux but never deal before with chroot and binary editing. I read the linked answer but not sure if will be easy for me to do it... – Repp 3/9, 2015 at 15:48

For another instance of Glibc, download gcc 4.7.2, for instance from this github repo (although an official source would be better) and extract it to some folder, then update LD_LIBRARY_PATH with the path where you have extracted glib.

export LD_LIBRARY_PATH=$glibpath/glib-2.49.4-kgesagxmtbemim2denf65on4iixy3miy/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=$glibpath/libffi-3.2.1-wk2luzhfdpbievnqqtu24pi774esyqye/lib64:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=$glibpath/pcre-8.39-itdbuzevbtzqeqrvna47wstwczud67wx/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=$glibpath/gettext-0.19.8.1-aoweyaoufujdlobl7dphb2gdrhuhikil/lib:$LD_LIBRARY_PATH

This should keep you safe from bricking your CentOS*.

*Disclaimer: I just completed the thought it looks like the OP was trying to express, but I don't fully agree.

Lockout answered 14/10, 2016 at 11:40 Comment(0)

download rpm packages and run the following command:

rpm -Uvh glibc-2.15-60.el6.x86_64.rpm \
glibc-common-2.15-60.el6.x86_64.rpm \
glibc-devel-2.15-60.el6.x86_64.rpm \
glibc-headers-2.15-60.el6.x86_64.rpm

Recreation answered 25/1, 2018 at 12:59 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Recommended topics

Hot tags