Yes, I and many others had the same problem, it happens after unmerging gccToday I did a sync and upgrade, which I haven't done for several days. There's quite a few packages to upgrade, but I started with portage. Then I upgraded gentoolkit (as indicated by the portage post-install messages). Then I proceeded to upgrade gcc.
After that, I got the dreaded: /usr/bin/python: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
Being a reader of this list, I proceeded to run 'ldconfig'. Now everything is working fine again. Hopefully this info will help someone else.
I am running an 'x86' system.
(when installing a more recent version). The linker still looks for libstdc++.so.5
in the old directory. Running ldconfig fixes this, and points the linker to the new path.
IMO it is a bug, ldconfig should be run automatically after changing /etc/ld.so.conf.
I checked the log of the last gcc merge, and it didn't call ldconfig *after* the new
compiler (and the libs) have been installed.
-- [EMAIL PROTECTED] mailing list
