updating glibc-2.3.2 to glibc-2.3.4
 

Before any thing else i want to thanks for any support you can offer to me.

I have a Red Hat Enterprise Linux WS version 3, in a station Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686 i686 i386 GNU/Linux.

I finish install matlab version r2007b and i get a problem, it says that it needs glibc 2.3.4 or superior.

this is what I have done, but it still not working to me:

1-dowload from http://rpm.pbone.net/ glibc-2.3.4.src.rpm, I install it and it says that it was successfully installed, but when i tipe:

rpm -qa glibc

its shows only the old version i already have installed.

2.-download glibc, glibc-common, glibc-devel, glibc-headers, glibc-profile, glibc-utils all are version 2.3.4, and they mark errors to me of dependencies.

rpm -- test -- install glibc-2.3.4-2.i386.rpm
error: Failed dependencies:
glibc-common = 2.3.4-2 is needed by glibc-2.3.4-2

nscd = 1.17.10-1 is needed by nscd-2.3.4-2
libselinux.so.1 is needed by nscd-2.3.4-2

rpm -- test -- install libselinux-1.19.1-7.i386.rpm
error: Failed dependencies: libc.so.6(GLIBC_2.3.4) is needed by libselinux-1.19.1-7

Does any body have a comment of what am i doing wrong? Does any body knows what i have to do to update my glibc without damaging any thing else that is already running?.

I have the cds of a Red HAT enterprise linux v.4 for 32 bits x86 and have checked that glibc version 2.3.4 is there, but i dont know how to update it in my system.

thanks for the attention.

glibc is sort of the single most important package on your system, against which everything else links and without which nothing else will run. It's not really safe to poke it too much unless you've got good backups and a way to restore from them that doesn't depend on that system working. Just saying.

The safest (and probably the only really safe) way to proceed would be to upgrade from your aging os release to a more current one. If you have the rhel 4 cds, that should be fairly straightforward. You could even go totally nuts and upgrade to 5. Or, if you don't have service anymore and don't want to renew, you could pretty easily hop over to CentOS.

Either way, I would really not recommend just trying to drop in a replacement glibc unless it's coming through the update mechanism directly.

I have to admit to having tried to upgrade Glibc by hand several times in the past. The commonest outcome was needing to reinstall the OS. Dont bother doing it unless you have time to rebulid almost every package on your system against the new glibc. It is possible but it will take the average person weeks to finish up.

Upgrade to a newer version of RHEL, or try out Centos.