From: Erik Andersen <andersen@codepoet.org>
To: buildroot@busybox.net
Subject: [Buildroot] libgcc_s.so.1 missing from filesystem
Date: Tue, 17 Oct 2006 13:03:19 -0600 [thread overview]
Message-ID: <20061017190319.GA19820@codepoet.org> (raw)
In-Reply-To: <452CE9EC.4050101@lambsys.com>
On Wed Oct 11, 2006 at 07:56:12AM -0500, David Lambert wrote:
> I built several utilities including python using buildroot. A commom
> problem seems to be that they depend on a library libgcc.so.1 which
> appears in buildroot/build_arm/staging_dir/lib/libgcc_s.so.1, but does
> not get transferred to the target filesystem. Manually moving it to the
> target appears to be a workaround. Is there a more elegant solution?
> What is this library?
Could I have a copy of your buildroot .config file? I've tested
both with and without BR2_GCC_SHARED_LIBGCC set and both settings
produced working root filesystems for me....
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2006-10-17 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 12:56 [Buildroot] libgcc_s.so.1 missing from filesystem David Lambert
2006-10-11 13:27 ` Fredrik Roubert
2006-10-11 13:30 ` Ashwin Bihari
2006-10-17 19:04 ` Erik Andersen
2006-10-17 19:36 ` Ashwin Bihari
2006-10-17 19:03 ` Erik Andersen [this message]
2006-10-18 12:12 ` David Lambert
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=20061017190319.GA19820@codepoet.org \
--to=andersen@codepoet.org \
--cc=buildroot@busybox.net \
/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