gcc installs anyway even if ebuild test fails. This is annoying, since the build dir is subsequently cleaned, so unless you have a huge scrollback you can't actually figure out what failed. In /var/log/elog/summary.log: >>> Messages generated by process 8506 on 2009-04-06 12:52:09 UTC for package sys-devel/gcc-4.3.2-r3: WARN: test check failed and that sucks :( WARN: postinst If you have issues with packages unable to locate libstdc++.la, then try running 'fix_libtool_files.sh' on the old gcc versions. Reproducible: Always Steps to Reproduce:
*** This bug has been marked as a duplicate of bug 253926 ***