From: Sergey Mironov <ierton@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] libgcc_s.so and gcc-config on embedded system
Date: Sat, 5 Mar 2011 21:23:43 +0300 [thread overview]
Message-ID: <AANLkTi=Et5LQso_P-KZqpA10233d0z9tL2Pkh-GcCEuh@mail.gmail.com> (raw)
Hi. I recently faced (probably well-known) problem while setting up my embedded
/usr/arm-module3-linux-gnueabi system tree. The problem is that
/lib/libgcc_s.so does not exist. Here is typical error message:
~ # bash
bash: error while loading shared libraries: libgcc_s.so.1: cannot open
shared object file: No such file or directory
I know that there is a workaround - copying this lib from
/usr/lib/gcc/.. to /usr/lib (paths are relative to arm's root). Also,
manual [1] suggests installing gcc on target system and using host's
gcc-config. I tried it and failed. My actions were:
emerge-arm-module3-linux-gnueabi gcc
ROOT=/usr/arm-module3-linux-gnueabi gcc-config -l
I looked inside host's gcc-config. Looks like it only works with
NATIVE compiler's libgcc_s.so. It treats arm's gcc as cross-compiler
despite the fact that arm's gcc is actually native for arm system.
Well, I install gcc-config on arm. It turns out, that gcc-config
depends on libgcc_s itself.
~ # gcc-config
/bin/bash: error while loading shared libraries: libgcc_s.so.1: cannot
open shared object file: No such file or directory
Funny. Should I mail gcc-config bug?
Sergey.
[1] http://gentoo.mindzoo.de/index.cgi/wiki/Cross%20Install
[2] http://www.gossamer-threads.com/lists/gentoo/amd64/190796
next reply other threads:[~2011-03-05 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 18:23 Sergey Mironov [this message]
2011-03-05 18:33 ` [gentoo-embedded] Re: libgcc_s.so and gcc-config on embedded system Sergey Mironov
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='AANLkTi=Et5LQso_P-KZqpA10233d0z9tL2Pkh-GcCEuh@mail.gmail.com' \
--to=ierton@gmail.com \
--cc=gentoo-embedded@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