From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] MTD build failing: undefined ref's to bcopy, bcmp
Date: Thu, 7 Jan 2010 22:30:30 +0000 (UTC) [thread overview]
Message-ID: <hi5na6$ngt$2@ger.gmane.org> (raw)
In-Reply-To: hi57as$vp6$1@ger.gmane.org
On 2010-01-07, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2010-01-07, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>> 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 ?
>
> Yes. :)
>
> It's an external toolchain that was generated by buildtoot.
The problem is that buildroot expects to find libgcc,
libstdc++, et al in $(SYSROOT)/lib
That's not where buildroot puts them.
Buildroot puts them in $(SYSROOT)/usr/arm-linux-uclibc/lib
Apparently, toolchains built by Buildroot aren't suitable for
use as external toolchains without some post-build massaging.
--
Grant Edwards grante Yow! I brought my BOWLING
at BALL -- and some DRUGS!!
visi.com
next prev parent reply other threads:[~2010-01-07 22:30 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
2010-01-07 17:57 ` Grant Edwards
2010-01-07 22:30 ` Grant Edwards [this message]
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='hi5na6$ngt$2@ger.gmane.org' \
--to=grant.b.edwards@gmail.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