From: Vaeth <vaeth@mathematik.uni-wuerzburg.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gcc4.7.2-r1 to 4.7.3 upgrade - hosed system?
Date: Fri, 17 May 2013 06:53:05 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1305170644360.6917@wma7001.mathematik.uni-wuerzburg.de> (raw)
In-Reply-To: <la50K-7d0-27@gated-at.bofh.it>
> # 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).
next parent reply other threads:[~2013-05-17 4:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <la50K-7d0-27@gated-at.bofh.it>
2013-05-17 4:53 ` Vaeth [this message]
2013-05-17 7:33 ` [gentoo-user] gcc4.7.2-r1 to 4.7.3 upgrade - hosed system? Adam Carter
2013-05-17 18:18 ` [gentoo-user] " walt
2013-05-18 9:53 ` Adam Carter
2013-05-18 10:22 ` walt
2013-05-18 10:25 ` Adam Carter
2013-05-16 11:49 [gentoo-user] " Adam Carter
2013-05-16 14:37 ` Daniel Troeder
2013-05-16 15:30 ` Adam Carter
2013-05-17 16:52 ` Chris Walters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1305170644360.6917@wma7001.mathematik.uni-wuerzburg.de \
--to=vaeth@mathematik.uni-wuerzburg.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox