> /usr/libexec/gcc/i686-pc-linux-gnu/4.4.4/cc1: error while loading shared > libraries: libmpfr.so.1: cannot open shared object file > > Meaning, run revdep-rebuild :)
Yeah, right. So revdep-rebuild does its thing, finds out that gcc is broken and tries to rebuild it with the broken gcc :) In this case the only way out involves backups or binary packages, or doing a binary build of the old mpfr version on another machine with CFLAGS compatible to those in use on the target. What's strange however, is that AFAIK in order to avoid this kind of breakage system ebuilds such as mpfr never delete old library versions; they just print a warning saying that the old library has been kept around and should be manually deleted after running revdep-rebuild. On all my sytems the transition to dev-libs/mpfr-3 was handled this way; note that I am still using portage 2.1, so this has nothing to do with the "preserve" feature in 2.2. andrea
