Re: [gentoo-user] gcc4.7.2-r1 to 4.7.3 upgrade - hosed system?

[Adam Carter]

This is a bug in gcc-config: It removes the old link too early

> so that the tools needed to establish the new link do not work
> anymore. IIRC correctly, there was a bug reported, but apparently
> it is still not fixed.
>
> To repair it manually you must temporarily create the old link.
> Here are detailed instruction how to do this:
>
> 1. Since tools like "ln -s" will not work, it is best to use busybox.
> So first start busybox (e.g. "bb" or "bb sh" depending on your setup).
>
> 2. Then go to the gcc library parent directory: On amd64 this should be
> cd /usr/lib64/gcc/x86_64-pc-**linux-gnu
> On i686 this is instead
> cd /usr/lib/gcc/i686*
> On other architectures, I don't know.
>
> 3. Create the symlink from your old directory to the new.
> Given the subject, I guess this should be:
> ln -s 4.7.3 4.7.2
>
> 4. Now gcc-config should work
>
> 5. Remove the symlink again
> rm 4.7.2
>
> 6. Run your env-update as usual and resource the profile
>
> 7. Test that gcc-config is still working (it should).
>
>
Still no good;
# cd /usr/lib64/gcc/x86_64-pc-linux-gnu
# ls -l
total 8
drwxr-xr-x 7 root root 4096 Feb 20 16:31 4.6.3
lrwxrwxrwx 1 root root    5 May 17 17:17 4.7.2 -> 4.7.3
drwxr-xr-x 7 root root 4096 May 17 17:20 4.7.3
# gcc-config 2
 * Switching native-compiler to x86_64-pc-linux-gnu-4.7.3 ...
/usr/bin/python2.7: error while loading shared libraries: libgcc_s.so.1:
cannot open shared object file: No such file or directory

ewarn: error while loading shared libraries: libgcc_s.so.1: cannot open
shared object file: No such file or directory
ewarn: error while loading shared libraries: libgcc_s.so.1: cannot open
shared object file: No such file or directory