[lug] Weird glibc upgrade problem

D. Stimits stimits at idcomm.com
Wed Mar 21 17:10:56 MST 2001

lpotter wrote:
> At 13:11 3/21/2001 -0700, you wrote:
> >Has anyone else come across this nonsense? At first I thought I just
> >messed something up somewhere along the line. Until today when my
> >friend ran into the same thing, but with a different package manager,
> >same packages. I don't understand how trying to remove glibc could
> >result in such a disaster as this. Anyone thoughts?
> basically, everything runs off of glibc, except the kernel, I believe. A
> couple years ago, I did about the same thing, tried to uninstall it before
> reinstallling.
> Anymore, I gather the tar ball, ./configure make make install, and if
> theres still old libs around (which if your going from some dist package to
> tar balls, and do not specify where to install it, there will be) ,
> manually delete them.
> ljp

If the old libs are a different major or minor release number (as
opposed to patch level), it is actually useful to leave them in. The
linker can properly figure things out if something requests an old
version. Think "compatibility".

More information about the LUG mailing list