After several days of not updating because of the binutils downgrade I did not really want, I started and -u world today. Before downgrading binutils everything worked fine. After downgrading binutils nothing builds anymore. It either complains that: checking for C compiler default output file name... configure: error: C compiler cannot create executables or: libXY file not recognized: File format not recognized Reproducible: Always Steps to Reproduce: 1. have a nice working system with binutils-2.17.50.0.16 2. have a forced downgrade to binutils-2.17-r1 3. watch the fireworks. Actual Results: git, ppp, bash, binutils (I tried to re-emerge 2.17.50.0.16) don't built anymore. Expected Results: Everything should work, as it always did.
Created attachment 127295 [details] emerge --info --verbose output
Created attachment 127296 [details] build.log of failing ppp after binutils downgrade
Created attachment 127298 [details] the git build.log
Created attachment 127300 [details] and bash
Created attachment 127302 [details] and the log of binutils-2.17.50.0.16 for fun and profit
So don't do it. *** This bug has been marked as a duplicate of bug 184801 ***
don't do what?
(In reply to comment #7) > don't do what? Don't downgrade binutils; especially not after you've recompiled gcc.
I didn't had a choice, did I? And a warning wasn't there too. And if binutils downgrade can break systems, why isn't there a safeguard? With glibc you can't even go back a freaking -rX revision, because it might break something.
Sure you had a choice, had you read the documentation and adjusted your package.keywords accordingly. Next time don't mess with package versions that are unkeyworded for your arch.
I did not had any binutils entries in package.keywords when I installed 2.17.50.0.16 orginally. The only entry that is there is because I tried to re-emerge it after the 2.17-r1 disaster.
(In reply to comment #11) > I did not had any binutils entries in package.keywords when I installed > 2.17.50.0.16 orginally. Sure you did, otherwise you would not have been able to emerge it at all. It's keyworded alpha -*; read the other bug. No more pointless noise here, please.
