I tried to update GCC to the latest version (3.3.2) from 3.2(.2?). So I did an "emerge gcc". After this completed, several things stopped working, notably python, KDE, and the gentoo tools that require python (emerge, /etc-update). Trying to run python produced a message stating that libstdc++.so.5 could not be found, even though it was located in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2. I looked at /etc/ld.so.conf and it had a reference to /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.1, even though I had not had 3.3.1 previously installed on my machine. I was unable to find any references to 3.3.1 in /etc/env.d, they were all to 3.3.2. ld.so.conf states that it is automatically updated by etc-update, but this would not run because it uses python. To resolve the problem, I edited /etc/ld.so.conf and added the correct gcc lib directory (/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2) and ran ldconfig. After this python was able to find the necessary library and worked fine, so I ran etc-update, which also worked fine (and removed the references to the old library directories). This sounds a lot like bug 15288, but that involved updating to a previous version of gcc (3.2) and was over a year old (and resolved). Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Expected Results: X was starting on bootup then the system was falling back to a command prompt, as I had KDM configured as my display manager. "startx" would bring up X with a non-KDE window manager. python, emerge, etc-update, gcc-config would not work.
This same problem happened to me on all my frontline servers. The /etc/ld.so.conf file had the old libstc* path before the new one so when env-update/ldconfig ran the old information was used and is incorrect. This bug currently could hit all systems that are setup to do daily updates via "emerge -DU world" My solution was to remove the depricated path from /etc/ld.so.conf and run ldconfig.
Same here, but on my box simply running ldconfig solved it, since the (in /etc/ld.so.conf) still existing path /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3 was no longer existant (thanks to autoclean). I think the problem is that env-update sorts the lines of /etc/ld.so.conf alphabetically (ending up with the old version in front of the new one), since in /etc/env.d/05gcc LDPATH has both paths (/foo/3.3.2:/foo/3.2.3) in the right order.
*** This bug has been marked as a duplicate of 40694 ***
