Again and again and again - its always the same. After doing an gcc upgrade (in this case 3.3.4 -> 3.3.5) I'm unable to compile anything afterwards. After again, searching in the bug tracker, I find the solution: "run fix_libtool_files.sh <old_gcc_version>". It is annoying, because the gcc ebuilds DO NOT tell you, that you have to run this script - I check my logfiles in /var/log/portage/* ! It would be great, if the gcc ebuilds would honor this, or at least gcc-config, which is actually used to switch between gcc versions! I hope that this gets somehow automated, or I see myself and others again searching the bugtracker after the "libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/<old_gcc_version>/libstdc++.la' is not a valid libtool archive" error ...
BTW the bug 51922 and 64519 are open, because of this exact behaviour! I think that automating the "fix_libtool_files.sh" step after an gcc upgrade, will at least help to lower related sounding bug reports!
*** This bug has been marked as a duplicate of 73435 *** *** This bug has been marked as a duplicate of 73435 ***