I ran revdep-rebuild about a month ago, It asked to remerge gcc-4.1.2. I allowed it. Every revdep-rebuild I've run since then has asked to build it again. How do I get out of this loop? Here's my revdep-rebuild -pv:
camille ~ # revdep-rebuild -pv Configuring search environment for revdep-rebuild Checking reverse dependencies... Packages containing binaries and libraries broken by a package update will be emerged. Collecting system binaries and libraries... done. (/root/.revdep-rebuild.1_files) Collecting complete LD_LIBRARY_PATH... done. (/root/.revdep-rebuild.2_ldpath) Checking dynamic linking consistency... broken /usr/kde/3.5/lib/kde3/kfile_pdf.so (requires libpoppler-qt.so.1 libpoppler.so.1) broken /usr/lib/kde3/libkritapdfimport.so (requires libpoppler-qt.so.1 libpoppler.so.1) broken /usr/lib/neko/libneko.so (requires libgc.so.1) broken /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcjawt.la (requires /usr/lib/lib-gnu-java-awt-peer-gtk.la) broken /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgij.la (requires /usr/lib/libgcj.la) done. (/root/.revdep-rebuild.3_rebuild) Assigning files to ebuilds... done. (/root/.revdep-rebuild.4_ebuilds) Evaluating package order... done. (/root/.revdep-rebuild.5_order) All prepared. Starting rebuild... emerge --oneshot -pv =sys-devel/gcc-4.1.2 =kde-base/kdegraphics-3.5.7-r1 =app-office/koffice-1.6.3-r1 .......... These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-devel/gcc-4.1.2 USE="doc fortran gcj gtk mudflap nls (-altivec) -bootstrap -build -d (-hardened) -ip28 -ip32r10k (-multilib) -multislot (-n32) (-n64) -nocxx -objc -objc++ -objc-gc -test -vanilla" 0 kB [ebuild R ] kde-base/kdegraphics-3.5.7-r1 USE="arts gphoto2 imlib opengl pdf -debug -kdeenablefinal -openexr -povray -scanner -tetex -xinerama" 0 kB [ebuild R ] app-office/koffice-1.6.3-r1 USE="arts doc mysql -debug -postgres -xinerama" 0 kB Total: 3 packages (3 reinstalls), Size of downloads: 0 kB Build finished correctly. Removing temporary files... You can re-run revdep-rebuild to verify that all libraries and binaries are fixed. If some inconsistency remains, it can be orphaned file, deep dependency, binary package or specially evaluated library. camille ~ # -- [EMAIL PROTECTED] mailing list
