I just updated my GCC to 4.2 on my Sabayon 3.4a like it said in the wiki, everything went fine, GCC works, but when I run a revdep-rebuild, It always wants me to reemerge GCC. So the first time I thought ok, I did something wrong so I reemerged it with revdep-rebuild, then I wanted to check if everything was OK so I did a revdep-rebuild again, and surprise, it still wants me to reemerge GCC. So after 4 emerge GCC, I'm tired of it, how can I fix this?
Here is what I get when I do a revdep-rebuild --pretend:
Code: Select all
localhost pavanpe # revdep-rebuild --pretend Configuring search environment for revdep-rebuild Environment mismatch from previous run, deleting temporary files... 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/lib/gcc/i686-pc-linux-gnu/4.2.0/libgij.la (requires /usr/lib/libgcj.la) broken /usr/lib/gcj-4.2.0/libjvm.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 --pretend =sys-devel/gcc-4.2.0 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-devel/gcc-4.2.0 Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild. localhost pavanpe #