On Friday 05 May 2006 08:12, Graham Murray wrote: > "Hemmann, Volker Armin" <[EMAIL PROTECTED]> writes: > > glibc updates NEVER need a rebuild. > > > > Only if you change from gcc 3.X to 4.Y you have to rebuild. > > > > But not because of a glibc update. > > That is not always true. A glibc upgrade *can* require that *some* > packages are re-built. I am not an expert on Elf so this may not be > 100% correct. The problem can come from symbol versioning, where the > package is linked against static linked library. If this static > library contains references to symbols in glibc for which the glibc > upgrade has provided a new version, then sometimes both the static > library and applications linking against it need to be rebuilt.
a problem of a few, static linked apps - most of them are binary anyway - does not excuse a whole emerge -e world. btw, I did lots of glibc updates and never broke anything. -- gentoo-user@gentoo.org mailing list
