After the emerge, /etc/ld.so.conf still points to /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1. ldconfig runs and hoses shared library cache (ld.so.cache). Changed /etc/ld.so.conf to point to /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2, ran ldconfig and everything worked
I had a similar experience. Lots of time after installing gcc 3.2.2 I did a emerge clean and ld.so.conf started pointing to gcc 3.2.1 again.
An emerge clean or re-emerge would probably fix the issue but my emerge was no longer working as Python could not find libstdc++.so.5 anymore.
Seems to be an issue with portage that changed internal stuff like $T ... I am trying to resolve it with Nick. For now, do: # export LD_LIBRARY_PATH="<path to new gcc internal lib>:${LD_LIBRARY_PATH}" and then fix /etc/env.d/05gcc, and run env-update .. You could even run: # gcc-config <your CHOST>-3.2.2
I am seeing this as well. At the end of the emerge, I got the error: /var/tmp/portage/gcc-3.2.2/temp/fix_libtool_files.sh: line 40: [: too many arguments gawk: fatal: can't open source file `portage:' for reading (No such file or directory) which may be part of the problem. Martin's workaround does fix it for me, however.
Ok, I did some changes to try and prevent this in future: ---------------------- 09 Mar 2003; Martin Schlemmer <azarah@gentoo.org> gcc-3.2.2*.ebuild : Fix handling of fix_libtool_files.sh to be more $FILESDIR independant. We basically install it to /sbin now, and then call it from there. Also export LD_LIBRARY_PATH with new gcc library path in it to prevent gcc-config from borking when run. This will hopefully fix bugs #15288, #16632, #16797.
According to Azarah's final comment, this looks to be fixed, so I'll resolve it as such. This gcc is outdated anyways. If the issue is still present in newer versions, then re-open.
