Bug 131719

Summary:	gcc-config-1.3.13-r2 resets to first profile if current profile no longer available
Product:	Gentoo Linux	Reporter:	Ryan Hill (RETIRED) <rhill>
Component:	Current packages	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	genstef, jakub
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Ryan Hill (RETIRED) gentoo-dev

2006-04-29 14:17:34 UTC

root ~ # gcc-config -l
 [1] i686-pc-linux-gnu-3.3.6
 [2] i686-pc-linux-gnu-3.4.6
 [3] i686-pc-linux-gnu-4.0.3
 [4] i686-pc-linux-gnu-4.1.0
 [5] i686-pc-linux-gnu-4.1.1-pre20060426 *
 [6] i686-pc-linux-gnu-4.2.0-pre20060421

root ~ # emerge -v gcc-4.1.1_pre20060429

[snippity]

root ~ # gcc-config -l
 [1] i686-pc-linux-gnu-3.3.6 *
 [2] i686-pc-linux-gnu-3.4.6
 [3] i686-pc-linux-gnu-4.0.3
 [4] i686-pc-linux-gnu-4.1.0
 [5] i686-pc-linux-gnu-4.1.1-pre20060429
 [6] i686-pc-linux-gnu-4.2.0-pre20060421

Previously, emerging a new version of gcc that caused the profile you're currently using to be replaced would automatically switch to the new version.  This recently changed behaviour to falling back to the first profile available.  It makes sense that if you're using gcc-3.4.5 and you upgrade to 3.4.6, you'll end up using 3.4.6, not some other version.  With the current behaviour it's extremely easy for someone to miss the fact that the compiler was changed out from under them and end up compiling half their tree with an old gcc.  The only way i noticed was i couldn't load kde due to c++ abi breakage.

Comment 1 SpanKY gentoo-dev

2006-05-25 20:44:12 UTC


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