It's a circle! to install autoconf you need perl installed but it depends on libtool that depends on autoconf so emerge system tries to compile autoconf before libtool/db/gdbm/libperl/perl breaking autoconf when it looks for perl. Reproducible: Always Steps to Reproduce: 1.scripts/bootstrap.sh 2.emerge system 3. Actual Results: perl not found Expected Results: emerge system finishes Ya thats about it
"emerge system" fails for me too! portage isn't abled to handle cyclic dependencies (and i wonder, how that would ever be possible), but this need some kind of fix.
I thought it'd be helpful to connect the dots: http://forums.gentoo.org/viewtopic.php?t=221698
Oops, wrong dot! http://forums.gentoo.org/viewtopic.php?t=227002
Help! This is stopping me from yet another Gentoo powered server :'(
The gist of the kludge is to use USE='-gdbm' until it's fixed.
rac recommends against the gdbm "fix" as it prevents further debugging of the problem. I retract the kludge. Please post your emerge info and emerge -pv systems. :-)
In order to actually determine what is causing the circularity, BEFORE you do anything hacky like USE=-gdbm (OK) or using emerge --nodeps on something (bad), it would be very helpful to know the following: (A) emerge info (B) emerge -pv system (C) grep ">>> emerge" /var/log/emerge.log This would show what has been done in what order, and what is left to do.
Thanks to lonex in #gentoo for providing a scratch system for testing. Taking the libtool dependency out of the libtool eclass solves this issue. There are many places to break the circularity, and I felt that one was the cleanest at the moment. Changed in CVS.
should be resolved now with rac's fix to libtool.eclass
