I don't have the ability to re-open bug 94959 which is marked as RESOLVED - DUPLICATE of another bug. The reporter of bug 94959 did not completely understand the real issue. {He admits to a foggy memory} The problem is that after the upgrade to gcc-3.4.4 is complete, gcc-config needs to be run to point to i686-pc-linux-gnu-3.4.4{-hardened*}. Instead, the completion of the emerge of gcc-3.4.4 leaves gcc-config pointing to i686-pc-linux-gnu-3.4.3{-hardened*}. This means that the next emerge determines that the C compiler cannot make executables because it can't find libstdc++.so.6. Solution: # gcc-config i686-pc-linux-gnu-3.4.4 or -hardened {nopie, nopiessp, nossp} as per your own configuration. Reproducible: Always Steps to Reproduce: emerge gcc-3.4.4 arts-3.4.1 Expected Results: The gcc-3.4.4 should reset the appropriate environmental variable
Please note that the next emerge following the emerge of gcc-3.4.4 will generate different errors depending on it's ebuild. For example: # emerge gcc-3.4.4 vanilla-sources The emerge of vanilla-sources will abort with a message indicating that it can't write files. This means that different people will most likely report completely different problems with the same root cause.
There are various threads about this error, e.g. http://forums.gentoo.org/viewtopic-t-344483.html They als mention creating a symbolic link before gcc-config is possible. I can confirm that this method works.
*** This bug has been marked as a duplicate of 84961 ***
