Hello all, I had been thinking about possibly emerging icedtea. According to the link posted a few days ago gcc needed the gcj flag added so I did that and emerged gcc. However it seems to have caused an endless loop in revdep-rebuild. If I'm correct this is a bug that is almost 3 years old and still unfixed across many revs of gcc and all the system stuff that's related. The only possible solution I noticed in a very quick read seems to require hand manipulation of base file which I'm not going to do.
http://bugs.gentoo.org/show_bug.cgi?id=125728 Now, it seems that many don't see this problem. Have any of you discovered an emerge method around this? Thanks, Mark lightning ~ # revdep-rebuild -ip * 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 * Generated new 1_files.rr * Collecting complete LD_LIBRARY_PATH * Generated new 2_ldpath.rr * Checking dynamic linking consistency [ 30% ] * 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) [ 45% ] * 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) [ 100% ] * Generated new 3_broken.rr * Assigning files to packages * /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/libgcjawt.la -> sys-devel/gcc * /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/libgij.la -> sys-devel/gcc * !!! /usr/lib64/gcc/x86_64-pc-linux-gnu/4.1.2/libgcjawt.la not owned by any package is broken !!! * /usr/lib64/gcc/x86_64-pc-linux-gnu/4.1.2/libgcjawt.la -> (none) * !!! /usr/lib64/gcc/x86_64-pc-linux-gnu/4.1.2/libgij.la not owned by any package is broken !!! * /usr/lib64/gcc/x86_64-pc-linux-gnu/4.1.2/libgij.la -> (none) * Generated new 4_raw.rr and 4_owners.rr * Cleaning list of packages to rebuild * Generated new 4_pkgs.rr * Assigning packages to ebuilds * Generated new 4_ebuilds.rr * Evaluating package order * Generated new 5_order.rr * All prepared. Starting rebuild emerge --oneshot --pretend sys-devel/gcc:4.1 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-devel/gcc-4.1.2 * Now you can remove -p (or --pretend) from arguments and re-run revdep-rebuild. lightning ~ #
