| 1 |
On 5/16/2013 7:49 AM, Adam Carter wrote: |
| 2 |
> My system no longer had a /lib64/libgcc_s.so.1 which made it quite unhappy. I |
| 3 |
> eventually copied one over from a fedora live iso i had and things are |
| 4 |
> operational again. Is there some way i can confirm if it was the gcc upgrade? |
| 5 |
> |
| 6 |
> This looks damning; |
| 7 |
> |
| 8 |
> # gcc-config 2 |
| 9 |
> * Switching native-compiler to x86_64-pc-linux-gnu-4.7.3 ... |
| 10 |
> /usr/bin/python2.7: error while loading shared libraries: libgcc_s.so.1: cannot |
| 11 |
> open shared object file: No such file or directory |
| 12 |
> |
| 13 |
> ewarn: error while loading shared libraries: libgcc_s.so.1: cannot open shared |
| 14 |
> object file: No such file or directory |
| 15 |
> ewarn: error while loading shared libraries: libgcc_s.so.1: cannot open shared |
| 16 |
> object file: No such file or directory |
| 17 |
|
| 18 |
Strange. I did not have the same problem. Of course, I didn't run gcc-config, |
| 19 |
since 4.72-r1 and 4.7.3 are in the same slot. |
| 20 |
|
| 21 |
After I merged the new one, I just did: |
| 22 |
|
| 23 |
source /etc/profile |
| 24 |
emerge -e system |
| 25 |
then |
| 26 |
emerge -e world |
| 27 |
|
| 28 |
I'll try switching it with gcc-config once I get back into Gentoo. (Currently |
| 29 |
running the Windows part of my dual boot system - waiting forever for a backup |
| 30 |
to finally finish. |
| 31 |
|
| 32 |
Chris |
Archives