Bug 188133

Summary:	downgrade to binutils-2.17-r1 from 2.6.17.50.0.16 screwed my system
Product:	Gentoo Linux	Reporter:	Volker Hemmann <volkerarmin>
Component:	[OLD] Core system	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	VERIFIED DUPLICATE
Severity:	major
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info --verbose output build.log of failing ppp after binutils downgrade the git build.log and bash and the log of binutils-2.17.50.0.16 for fun and profit

Description Volker Hemmann 2007-08-08 17:13:19 UTC

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.

Comment 1 Volker Hemmann 2007-08-08 17:14:13 UTC

Created attachment 127295 [details]
emerge --info --verbose output

Comment 2 Volker Hemmann 2007-08-08 17:14:53 UTC

Created attachment 127296 [details]
build.log of failing ppp after binutils downgrade

Comment 3 Volker Hemmann 2007-08-08 17:15:30 UTC

Created attachment 127298 [details]
the git build.log

Comment 4 Volker Hemmann 2007-08-08 17:16:24 UTC

Created attachment 127300 [details]
and bash

Comment 5 Volker Hemmann 2007-08-08 17:17:39 UTC

Created attachment 127302 [details]
and the log of binutils-2.17.50.0.16 for fun and profit

Comment 6 Jakub Moc (RETIRED) gentoo-dev

2007-08-08 18:15:19 UTC

So don't do it.

*** This bug has been marked as a duplicate of bug 184801 ***

Comment 7 Volker Hemmann 2007-08-08 18:21:22 UTC

don't do what?

Comment 8 Jakub Moc (RETIRED) gentoo-dev

2007-08-08 18:22:38 UTC

(In reply to comment #7)
> don't do what?

Don't downgrade binutils; especially not after you've recompiled gcc.

Comment 9 Volker Hemmann 2007-08-08 18:26:01 UTC

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.

Comment 10 Jakub Moc (RETIRED) gentoo-dev

2007-08-08 18:29:58 UTC

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.

Comment 11 Volker Hemmann 2007-08-08 18:36:24 UTC

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.

Comment 12 Jakub Moc (RETIRED) gentoo-dev

2007-08-08 18:37:46 UTC

(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.