CentOS 6 - Update GLIBC (libc.so.6)

I'm trying to update glibc from 2.12 to 2.14.

I've tried this:
yum install ftp://rpmfind.net/linux/fedora/linux/updates/15/x86_64/glibc-2.14.1-6.i686.rpm
yum update ftp://rpmfind.net/linux/fedora/linux/updates/15/x86_64/glibc-2.14.1-6.i686.rpm

But either way it says:
Examining /var/tmp/yum-root-wKTjts/glibc-2.14.1-6.i686.rpm: glibc-2.14.1-6.i686
Marking /var/tmp/yum-root-wKTjts/glibc-2.14.1-6.i686.rpm as an update to glibc-2.12-1.47.el6_2.9.x86_64
No Packages marked for Update

And then the version is still 2.12.

Any ideas!?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


yum -Uvh --nosignature ftp://rpmfind.net/linux/fedora/linux/updates/15/x86_64/glibc-2.14.1-6.i686.rpm..

Once you run this if there is any error, please copy paste the error completely
ADFBAuthor Commented:
I get this yum error:

yum -Uvh --nosignature ftp://rpmfind.net/linux/fedora/linux/updates/15/x86_64/glibc-2.14.1-6.i686.rpm

Command line error: no such option: -U
oops sorry typo

rpm -Uvh --nosignature ftp://rpmfind.net/linux/fedora/linux/updates/15/x86_64/glibc-2.14.1-6.i686.rpm

Please copy paste the output if unsuccessful, I think there are some dependencies that needs to be addressed.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

ADFBAuthor Commented:
error: Failed dependencies:
        glibc-common = 2.14.1-6 is needed by glibc-2.14.1-6.i686
        libfreebl3.so is needed by glibc-2.14.1-6.i686
        libfreebl3.so(NSSRAWHASH_3.12.3) is needed by glibc-2.14.1-6.i686
ADFBAuthor Commented:
Should I not also be using x86_64, because it's a 64-bit system?
Download the required glibc-common and glibc from the site and issue the below command. It should solve your issue.

yum localinstall --disablerepo=* glibc-common-glibc-2.14.rpm glibc-2.14.rpm

Yes you need to use  x86_64 instead of i686
Download and save glibc-common-2.14.1-6.x86_64.rpm and glibc-2.14.1-6.x86_64.rpm to localdrive.

run the command

yum localinstall --disablerepo=* glibc-common-2.14.1-6.x86_64.rpm glibc-2.14.1-6.x86_64.rpm
Using the versions for fedora 15 from rpmfind instead of from the CentOS 6 repos is probably going to break your server in short order.

The CentOS 6.x kernels are from between fedora 12 and 14 timeline... that's why it still uses GNOME 2.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Why do you want to update glibc on CentOS 6?

Updating glibc is generally problematic.  There are kernel and library dependencies.  It's easy to have your system become unusable.  As @Darr247 mentions, if you pick and chose RPMs from other distributions, you are likely to trash your system.

You asked for ideas:
  1)  Don't replace glibc.  If you do then
  2)  Make a full image backup of your system before trying this
  3)  Don't use yum
  4)  Install ALL related dependencies in one call to "rpm"
If you're doing this to run the latest versions of Chrome, you should use Richard Lloyd's script from

His script installs the most-recent version of glibc (that doesn't crash C6) segregated in its own folder so only Chrome uses it, which should keep your server from getting corrupted by incorrect versions of supported libraries.
This info is still relevant now and will remain relevant for the support-life of CentOS 6 (sometime in 2020).

I suggest a split with these 3 posts:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.