This bug started out as some comments in bug #68395, especially #4, #6, #7 and #9. It seems to happen that users update their gcc and then remove the now-obsolete version. However, sometimes they remove the old version without first using gcc-config to switch to the new version (and therefore they remove their currently active gcc profile). Yes, this is wrong and bad and they deserve to be kicked. But it happens to the best of us. The problem is, after noticing one's mistake and trying to use gcc-config to switch to the new gcc profile, gcc-config complains: * gcc-config: Active gcc profile is invalid! * Switching native-compiler to x86_64-pc-linux-gnu-4.3.2... * gcc-config: Active gcc profile is invalid! * Your gcc has a bug with GCC_SPECS. * Please re-emerge gcc. * http://bugs.gentoo.org/68395 Experienced users might now notice the "active gcc profile is invalid" message and just run gcc-config again, and voila, everything works fine. (Actually, it worked fine before, but threw an error anyway.) However, inexperienced users might really re-emerge gcc and curse Gentoo for it (as gcc takes quite some time). Please make this message more intelligent. When switching from an invalid profile to a valid one, no re-merge suggestion should appear.
I just hit this on my first sync+upgrade since I installed the most recent Gentoo a couple of weeks ago. It was a gcc upgrade from 4.3.2-r5 to 4.3.4 - i.e. same slot. I think what caused the error message was that emerge in this case uninstalled the old version, from the same slot, leaving no other gcc. FWIW, GCC_SPECS existed and was "". gcc-config reports the right value afterwards, and everything looks OK apart from the error message...
(In reply to comment #1) I saw this too, on a completely clean "emerge --deep --update system" in an environment that I have not tweaked in any way (in particular I have not set GCC_SPECS, although it *is* set to the empty string - apparently the default?) It happens in the 'switching the native compiler' step, despite this gcc --version says I have 4.3.4 (not the previous version, 4.3.2) so presumably everything is ok - just the error message that is wrong.
partially fixed here: http://sources.gentoo.org/eclass/toolchain.eclass?r1=1.413&r2=1.414 the rest should be addressed in gcc-config-1.5
It also happens after an update of gcc, for example from 4.4.2 to 4.4.3 as it removes the old version before switching to the new one.
Hmm, still happens here (between gcc-4.4.3 and gcc-4.4.4), message is misleading a bit.
But it's with gcc-config-1.4.1 so I think it explains this.
If this really is resolved in 1.5, why is 1.5 still KEYWORD masked for all arches? It was added in that state in December 2009 and no updates have been done since then. Is 10 months long enough for something to be tested for =) ? I've hit this bug twice in the last year!.
It's still happening. Reopening the bug since gcc-config-1.5 is not even ~arch.
+1 Ran into this when seeing that gcc-4.4.4-r2 went to amd64 stable on hardened profile, and running 'emerge -uav gcc' as gcc upgrade guide suggests. If gcc-config-1.5 fixes this, then please stabilize. There seem to be no open bugs against it.
unless you have info on gcc-config-1.5 not working, this is FIXED
(In reply to comment #10) > unless you have info on gcc-config-1.5 not working, this is FIXED > Huh? gcc-config-1.5 is hard-masked. It by default, does not work. It needs to be given a keyword in order for people to ascertain it working or not ( or they need to unkeyword mask it ).
brand new fresh off the nightly ISO install. still popping the message that you need to rebuild gcc.
Shouldn't a bug be opened against whoever is responsible for un-hard-masking gcc-config-1.5? Wouldn't SpanKY know exactly who that should be, since SpanKY closed this bug? And shouldn't that bug be commented here? Or do folks want to keep on seeing noise on this bug for years and years and years...
This just happened to me, too. What is needed so that gcc-config-1.5 can be stabilized? how can we help?
Just hit this. Two years?
Happy Birthday!
Just hit this bug. Any plans to make gcc-config-1.5 available to the general public?
It has been for two months now.
