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 06:46:30 +0000 (UTC) [thread overview]
Message-ID: <hi4006$nin$1@ger.gmane.org> (raw)
In-Reply-To: hi3tpb$k7d$1@ger.gmane.org
On 2010-01-07, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> Is BR2_PACKAGE_MTD/BR2_PACKAGE_MTD_UTILS actually what I need
>> to provide mtd.h for building the u-boot env set/get target
>> tools, or does mtd.h come from somewhere else?
It's actually mtd/mtd-user.h that's missing. It looks like it
should come from the kernel headers. It's there in the kernel
source tree (and in /usr/include on my development hosts), but
it's missing from the toolchain's usr/include directory.
How do you get mtd/*.h header files included in /usr/include
when the toolchain is built?
--
Grant
next prev parent reply other threads:[~2010-01-07 6:46 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 [this message]
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
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='hi4006$nin$1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.