From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] MTD build failing: undefined ref's to bcopy, bcmp
Date: Thu, 7 Jan 2010 18:37:09 +0100 [thread overview]
Message-ID: <20100107183709.74ba1341@surf> (raw)
In-Reply-To: <hi5437$id4$1@ger.gmane.org>
Le Thu, 7 Jan 2010 17:02:31 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :
> I patched the bug in the mtd package so it's now building, but
> it won't run:
>
> # flash_info
> flash_info: can't load library 'libgcc_s.so.1'
>
> libgcc_s.so.1 appears in the staging directory,
>
> $ find . -name libgcc_s*
> ./output/staging/usr/arm-linux-uclibc/lib/libgcc_s.so
> ./output/staging/usr/arm-linux-uclibc/lib/libgcc_s.so.1
>
> but it's not present in the target filesystem.
Are you using a buildroot-generated toolchain or an external toolchain ?
> Am I having all of these problem becuase I shouldn't be using
> HEAD, or am I doing something else wrong?
The MTD utils package has very recently been updated into HEAD, which
might explain why you're encountering so many failures.
http://git.buildroot.net/buildroot/commit/?id=9400c73582326c543fae82120af3904836145655
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-01-07 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 23:43 [Buildroot] MTD build failing: undefined ref's to bcopy, bcmp Grant Edwards
2010-01-07 6:08 ` Grant Edwards
2010-01-07 6:46 ` Grant Edwards
2010-01-07 17:02 ` Grant Edwards
2010-01-07 17:37 ` Thomas Petazzoni [this message]
2010-01-07 17:57 ` Grant Edwards
2010-01-07 22:30 ` Grant Edwards
2010-01-08 7:57 ` Thomas Petazzoni
2010-01-17 23:29 ` Peter Korsgaard
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=20100107183709.74ba1341@surf \
--to=thomas.petazzoni@free-electrons.com \
--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