revdep-rebuild finds bogus dynamic linking inconsistencies in the GCC package on multilib AMD64 systems. Output is: Checking dynamic linking consistency... broken /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/libgcjawt.la (requires /usr/lib/../lib64/lib-gnu-java-awt-peer-gtk.la) broken /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/libgij.la (requires /usr/lib/../lib64/libgcj.la) broken /usr/lib64/gcc/x86_64-pc-linux-gnu/4.1.2/libgcjawt.la (requires /usr/lib/../lib64/lib-gnu-java-awt-peer-gtk.la) broken /usr/lib64/gcc/x86_64-pc-linux-gnu/4.1.2/libgij.la (requires /usr/lib/../lib64/libgcj.la) done. (/root/.revdep-rebuild.3_rebuild) This error persists even if you actually rebuild the package. It also persists if you run revdep-rebuild --ignore. It's still there (in unchanged form) after the most recent update from GCC-4.1.1-r3 to GCC-4.1.2. I suspect it only happens on multilib systems, but I could be wrong. Unfortunately, this compromises the usability of revdep-rebuild considerably, since GCC takes way too long to compile the GCC package to just build it "on the side", even on cutting edge hardware. (I hope "ebuilds" isn't the completely wrong section...) Reproducible: Always Steps to Reproduce: Run revdep-rebuild on a multilib AMD64 system. Possibly java needed in USE flags. Should you have problems reproducing it, I can provide full USE flags for my system.
*** This bug has been marked as a duplicate of bug 125728 ***
