What I first tried to do was to install the newer version of glibc
(using rpm) while my older version was still installed - no go, I
received error messages about conflicts with the older glibc so and
other files. I then tried to uninstall the older version but received
error messages concerning all the utilities that depended on it.
In looking at the man page for rpm, the command "rpm -e -nodeps
<package-name>" may work, and if it did and I was able to install the
newer version, would the dependent programs "find" that version and
function as usual?
No, that won't work, you will render your installation useless.
Use the upgrade option, I'm pretty sure you had found it if you had read the
man page a bit better.
rpm -Uvh glibc-x.y.c-z.arch.rpm
> and if it did and I was able to install the
> newer version, would the dependent programs "find" that version and
> function as usual?
This depends on the version jump you would do.
--
//Aho
OK, I tried the -U option and I didn't get all the error messages I
got before. What error message I did get was:
"/sbin/ldconfig conflicts with file from ldconfig-1.9.5-8
error: glibc-2.2.2-53.i386.rpm cannot be installed"
When I query my currently installled glibc, it shows that the original
version is still installed. So what's the deal with ldconfig? If I
uninstall it and then install a newer version of it after
(successfully??) installing glibc, maybe this will work.
Feel free to elaborate on ldconfig; I looked at the man page but am
still not sure what it's used for.