On Wed, 2006-08-09 at 15:10 -0700, Peter Scott wrote: > I have recently upgraded glibc, glibc-common and glibc-headers > from version 2.4-8 to 2.4.90-13, having run > yum check-update and finding these on the output. > > However a consequence was that gcc would no longer work > properly, failing at the loader (linker) stage. > > The reason appears to be that glibc-devel, which is normally > used by gcc, does not yet seem to have been upgraded to > 2.4.90-13, so there is a conflict, which was not detected by > yum. > There's no explicit conflict listed in the package. How would yum be able to know about it? > Is there a convenient way to UNDO the updating, i.e., to > re-install version 2.4-8 for the glibc* packages already > installed on my machine? (This would be the equivalent of > rpm -Uvh --oldpackage glibc-2.4-8....rpm etc.) and that would be the way to do it. -sv
