Summary: | emerge libsdl 1.2.8 r1 endless loop (old 'missing' script) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ocstemp |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ocstemp
2006-01-31 22:44:26 UTC
*** Bug 121123 has been marked as a duplicate of this bug. *** Check your filesystem and disk space available and upgrade your toolchain {binutils, glibc, gcc) before reporting bugs. Amusingly enough, I ran into this problem while verily trying to '--update world' in preparation for a freevo install. Anyhow, I finally corrected the issue with the following steps, in this exact order: 1) emerge --sync 1) FEATURES="-maketest -sandbox" emerge --update gcc 2) FEATURES="-maketest -sandbox" emerge --update binutils 1) FEATURES="-maketest -sandbox" emerge --update make 1) FEATURES="-maketest -sandbox" emerge --update glibc 1) FEATURES="-maketest -sandbox" emerge --update libtool 1) emerge --update world Might I submit that there be some sort of error check for infinitely-looping ebuilds? Or at least a priority placed on the toolchain in '--update world'? Anyways, thanks for the advice. |