Bob Young wrote:
After a recent emerge -DuN world, messages for one of the packages stated
that it was necessary to run revdep-rebuild after emerging the package, so I
did. The revdep-rebuild ended up merging six packages, with one of them
being gcc. Emerging all six packages took several hours, and I noticed that
gcc by itself took a significant amount of time.
The final message stated that I could re-run revdep-rebuild to verify that
all inconsistencies had been resolved, unfortunately, I did not add a -p to
the command and to my surprise it spent the next couple of hours or so
emerging gcc again.
After that finished, I again ran revdep-rebuild although this time with a -p
and below is the output:
<< SNIP >>
How do I determine if this is a case of "orphaned file, deep dependency,
binary package or specially evaluated library" and, if it is one of those,
how do I determine which one, and then how do I fix this...?
Thanks for listening,
Bob Young
San Jose, CA
This may help: http://bugs.gentoo.org/show_bug.cgi?id=125728 I'm not
sure what changed but mine does not do this any more. I'm using
app-portage/gentoolkit-0.2.3-r1 at the moment.
Dale
:-) :-)
--
gentoo-user@lists.gentoo.org mailing list