Fixing a broken toolchain

Message

nick24 · Post by **nick24** » Wed Nov 04, 2009 11:32 am

When I updated my system (emerge -DuN system) yesterday, I couldn't install binutils 2.19-r3 because it had three unexpected errors found in the test suite (having to do with shared libraries). I couldn't find any existing bug reports about this, so I assumed it was my toolchain that was at fault. I tried re-emerging the entire base system to fix any problems that would cause binutils to break, but it also choked on other packages like m4, with a few tests failing in the test suite. I also rebuilt glibc and linux, which worked fine, but did nothing to help.

So, what is the best way to fix a toolchain that is producing programs that fail tests? And is there some way to force things to install without running tests, so I can at least update my system? Obviously, I tried setting the -test use flag, which was overridden.

Thanks!

few · Post by **few** » Wed Nov 04, 2009 12:19 pm

a) Having test suits fail doesn't necessarily mean that your toolchain is broken. But without error messages no one can tell what's wrong. bugzilla might be the better place for this.
b) Why do you ran the tests for all that stuff?
c) The correct way to enable/disable tests with portage is the FEATURES variable, not the use flag.
d) Are you using a dev profile? (eslect profile list) If yes, why? They are for gentoo devs.

Mike Hunt · Post by **Mike Hunt** » Wed Nov 04, 2009 1:55 pm

Please post your emerge --info

nick24 · Post by **nick24** » Wed Nov 04, 2009 8:38 pm

@few:

Facepalm. I guess d was my problem. I must have selected the dev profile by mistake, when I just did a profile update. I guess those tests aren't supposed to all pass then. Everything installs fine now.

Thanks!