i am submitting this bug on behalf of my friend. When he emeged gcc 3.3, he noticed that Portage did not 'emerge clean' afterwards. This might cause consequent problems in other places.. rm -rf /usr/lib/libgcc_s.so.1 ln -s /usr/lib/gcc-lib/i686-pc-linux-gnu/3,3/libgcc_s.so.1 /usr/lib these two lines would have to be added in line 550 around. Reproducible: Always Steps to Reproduce:
So what command did he use to merge it, and did he have the '/usr/lib/libgcc_s.so.1' symlink?
*** Bug 21587 has been marked as a duplicate of this bug. ***
ln -s /usr/lib/gcc-lib/i686-pc-linux-gnu/3,3/libgcc_s.so.1 /usr/lib/ i missed out / at the end.. the guy is away for 2 or 3 days, i will let him to produce some more evidence or solution ;)
no info till yet
fixed with latest portage and gcc