A few days ago, when gcc-3.3.2-r5 went stable, I did the upgrade. Then I got the dreaded error message about python not being able to load libstdc++. I fixed this ok, then looked around on my system and found the following: In the gcc-3.3.2-r5 ebuild, slot is set to 3.2. Also, in the log for the gcc 3.3.2 installation it appears that gcc-config didn't work -- here is the output from that. postinst /usr/sbin/gcc-config: Could not source /etc/init.d/functions.sh! * Scannig libtool files for hardcoded gcc library paths... If I could hazzard a guess at what happened, when I did the upgrade, gcc-3.3.2-r5 was merged successfully, then gcc-config was unable to change the gcc compiler profile, so the system was still configured to use gcc 3.2.3-r3. Then gcc-3.2.3-r3 was unmerged, which left the system unable to find the c++ library. Reproducible: Always Steps to Reproduce: 1. start with a system that has gcc-3.2.3-r3 installed. 2. upgrade to gcc-3.3.2-r5 3. Actual Results: Nothing that was written in c++ would run; the system could not load the libstdc++.so.5 shared library.
*** This bug has been marked as a duplicate of 40955 ***
