On 5/16/2013 7:49 AM, Adam Carter wrote:
My system no longer had a /lib64/libgcc_s.so.1 which made it quite unhappy. I
eventually copied one over from a fedora live iso i had and things are
operational again. Is there some way i can confirm if it was the gcc upgrade?
This looks damning;
# 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
Strange. I did not have the same problem. Of course, I didn't run gcc-config,
since 4.72-r1 and 4.7.3 are in the same slot.
After I merged the new one, I just did:
source /etc/profile
emerge -e system
then
emerge -e world
I'll try switching it with gcc-config once I get back into Gentoo. (Currently
running the Windows part of my dual boot system - waiting forever for a backup
to finally finish.
Chris
