3

How do I install glibc on a CentOS server?

I did:

yum install glibc-devel

But it tells me that the version glibc 2.15 is installed.

However i need to have the version 2.17.

Improve this question
  • 1
    Which CentOS version are you using ? – Dominik Feb 25 '10 at 11:12
5

You can find the official glibc versions for CentOS on the CentOS mirror sites.

For example

Improve this answer
  • 2
    both links are broken – oldboy Jun 23 '18 at 5:52
5

If you are absolutely sure you need it, you have two choices:

  1. use a different distribution that has the version you need (perhaps in a VM on top of your CentOS)
  2. Compile everything manually (I'd install rpm-build and use make rpm, but this might
    a) break dependencies in the system, and
    b) be a pretty complicated task to do, since the new version of glibc will require a lot of other prerequisites)
Improve this answer
4

Well, that means that CentOS only has version 2.15 in its repositories. You could try to use yum --enablerepo=updates-testing --enablerepo=testing install glibc-devel but be aware, that an incompatible glibc may lead to problems with installed programs.

Improve this answer
-5

To install glib on CentOS/RedHat/Fedora:

Login as root user via command prompt/shell

yum install glib*
Improve this answer
  • 3
    Don't ever go into system administration, then. That's exactly the opposite of best practice, which is to install nothing that isn't necessary. – Michael Hampton Jun 12 '14 at 3:07
  • 2
    @LinhLino You realize that this question is 4 YEARS old, and your solution simply installs all of the current glib packages in the repo rather than the specific version that at the time of the question was bleeding edge. – Jacob Jun 12 '14 at 3:23
  • 2
    When you are going to build source code, you may need it one time or another, so why not install it all first? Why not? Alright. Well, you asked... (1) Disk space (2) processor cycles (some things are services / daemons, so you install them once and you're paying forever) (3) your time (it takes a hell of a lot of time to install everything) (4) robustness (often, installing things requires removing other things, so good luck with the dependency nightmares you create) (5) security! More code on the system- especially more services with default passwords- means more attack vectors. – Parthian Shot Jul 31 '15 at 3:28
  • 2
    (6) Auditing! (related to security) Should what's happening right now be concerning? Is it indicative of a hack? If you install everything, who knows! You don't. If you don't know what should be happening, you can't tell when malware is on the system, which brings us to... (7) standards compliance! Installing everything is pretty much guaranteed to break whatever security compliance your company requires. (8) uptime; more applications means more code that might break your system- either due to exploitation or a simple bug. Also means that, when a server does fail, you'll take longer to – Parthian Shot Jul 31 '15 at 3:30
  • 1
    get back online, because you need to wait to install everything that GNU has ever written. – Parthian Shot Jul 31 '15 at 3:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.