the gcc binaries build correctly but the links are not made correctly from gcc-4.2.2 to gcc etc...so when you run emerge --depclean on the system.you are left without a valid compiler suite because it doesn't find the correct version of gcc. Reproducible: Always Steps to Reproduce: 1. build & install gcc 4.2.2 2. run emerge --depclean 3. compile a program.
I've just sym-linked the binaries of gcc-4.2.2 c++.4.2.2 gfortan-4.2.2 g++-4.2.2 to the shortened names without version number and I'm rebuilding gcc-4.2.2 now at the moment to see if it reproduces itself....
Ah I see what happened ...when you rebuild the compiler after the symbolic links where made your compiler suite gets rebuild correctly...however it is not normal that this happens. Becuase I used emerge -ev world to compile this gcc version.
There's absolutely no useful info here; please stop abusing bugzilla for similar things. http://www.gentoo.org/doc/en/bugzilla-howto.xml
(In reply to comment #3) > There's absolutely no useful info here; please stop abusing bugzilla for > similar things. > > http://www.gentoo.org/doc/en/bugzilla-howto.xml > (In reply to comment #3) > There's absolutely no useful info here; please stop abusing bugzilla for > similar things. > > http://www.gentoo.org/doc/en/bugzilla-howto.xml > sorry.... I knew I forgot something e.i. to post the important bit because I got three phone calls in between me starting to post this report & me finishing this thing .
You might want to review http://www.gentoo.org/doc/en/gcc-upgrading.xml... You use gcc-config to switch between gcc versions after upgrade, no NOT create any symlinks manually anywhere.
