Summary: | libtool needs autoconf/automake before perl has been compiled that needs libtool | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chad Corkrum <Chad_C_> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | sven.koehler |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chad Corkrum
2004-09-24 07:54:46 UTC
"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 |