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

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

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 790 bytes --]

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

[Daniel Troeder]

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

Am 16.05.2013 13:49, schrieb Adam Carter:
> 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
> 
I had the same yesterday - run:
LD_LIBRARY_PATH=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/ ldconfig
to fix your system.

Thanx to chithanh for this life-saving oneliner
(http://forums.gentoo.org/viewtopic-p-7053126.html).

Greetings,
Daniel


-- 
Get my PGP key at:
*
http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0x837FB8B5BB9D4887
* $ gpg --recv-keys --keyserver keyserver.ubuntu.com 0xBB9D4887


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

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

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 552 bytes --]

I had the same yesterday - run:

> LD_LIBRARY_PATH=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/ ldconfig
> to fix your system.
>
> Thanx to chithanh for this life-saving oneliner
> (http://forums.gentoo.org/viewtopic-p-7053126.html).
>
> Greetings,
> Daniel
>
>
That didnt help the gcc-config error, and also i notice that there's bits
of 4.7.2 still around;

 # ls -l /lib64/libgcc*
-rwxr-xr-x 1 root root 88720 May 16 21:13
/lib64/libgcc_s-4.7.2-20121109.so.1
lrwxrwxrwx 1 root root    28 May 17 01:19 /lib64/libgcc_s.so.1 ->
libgcc_s-4.7.2-20121109.so.1

[-- Attachment #2: Type: text/html, Size: 986 bytes --]

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

[Vaeth]

> # 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

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).

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

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2127 bytes --]

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

[Chris Walters]

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

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

[walt]

On 05/17/2013 12:33 AM, Adam Carter wrote:
> # 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

 #ldconfig -p | grep libgcc
        libgccpp.so.1 (libc6,x86-64) => /usr/lib64/libgccpp.so.1
        libgccpp.so (libc6,x86-64) => /usr/lib64/libgccpp.so
        libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
        libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
        libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
        libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
        libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
        libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
        libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
        libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so

What do you have?

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

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]

On Sat, May 18, 2013 at 4:18 AM, walt <w41ter@gmail.com> wrote:

> On 05/17/2013 12:33 AM, Adam Carter wrote:
> > # 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
>
>  #ldconfig -p | grep libgcc
>         libgccpp.so.1 (libc6,x86-64) => /usr/lib64/libgccpp.so.1
>         libgccpp.so (libc6,x86-64) => /usr/lib64/libgccpp.so
>         libgcc_s.so.1 (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
>         libgcc_s.so.1 (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
>         libgcc_s.so.1 (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
>         libgcc_s.so.1 (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
>         libgcc_s.so (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
>         libgcc_s.so (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
>         libgcc_s.so (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
>         libgcc_s.so (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so
>
> What do you have?
>
>
# ldconfig -p | grep libgcc
    libgcc_s.so.1 (libc6,x86-64) => /lib64/libgcc_s.so.1
    libgcc_s.so.1 (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
    libgcc_s.so.1 (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
    libgcc_s.so.1 (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
    libgcc_s.so.1 (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
    libgcc_s.so (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
    libgcc_s.so (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
    libgcc_s.so (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
    libgcc_s.so (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so

# ls -l /lib64/libgcc_s.so.1
lrwxrwxrwx 1 root root 28 May 17 19:11 /lib64/libgcc_s.so.1 ->
libgcc_s-4.7.2-20121109.so.1

Crufty.... Will it be safe to delete the link since the file is found in
the other locations?

[-- Attachment #2: Type: text/html, Size: 2781 bytes --]

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

[walt]

On 05/18/2013 02:53 AM, Adam Carter wrote:
> On Sat, May 18, 2013 at 4:18 AM, walt <w41ter@gmail.com <mailto:w41ter@gmail.com>> wrote:
> 
>     On 05/17/2013 12:33 AM, Adam Carter wrote:
>     > # 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
> 
>      #ldconfig -p | grep libgcc
>             libgccpp.so.1 (libc6,x86-64) => /usr/lib64/libgccpp.so.1
>             libgccpp.so (libc6,x86-64) => /usr/lib64/libgccpp.so
>             libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
>             libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
>             libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
>             libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
>             libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
>             libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
>             libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
>             libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so
> 
>     What do you have?
> 
> 
> # ldconfig -p | grep libgcc
>     libgcc_s.so.1 (libc6,x86-64) => /lib64/libgcc_s.so.1
>     libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
>     libgcc_s.so.1 (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
>     libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
>     libgcc_s.so.1 (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
>     libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
>     libgcc_s.so (libc6,x86-64) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
>     libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
>     libgcc_s.so (libc6) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so
> 
> # ls -l /lib64/libgcc_s.so.1
> lrwxrwxrwx 1 root root 28 May 17 19:11 /lib64/libgcc_s.so.1 -> libgcc_s-4.7.2-20121109.so.1
> 
> Crufty.... Will it be safe to delete the link since the file is found in the other locations?

Yes, then run ldconfig afterwards.

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

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 320 bytes --]

>
> > # ls -l /lib64/libgcc_s.so.1
> > lrwxrwxrwx 1 root root 28 May 17 19:11 /lib64/libgcc_s.so.1 ->
> libgcc_s-4.7.2-20121109.so.1
> >
> > Crufty.... Will it be safe to delete the link since the file is found in
> the other locations?
>
> Yes, then run ldconfig afterwards.
>
>
Thanks - gcc-config 2 runs cleanly now.

[-- Attachment #2: Type: text/html, Size: 598 bytes --]