From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where is mtd/mtd-user.h supposed to come from?
Date: Tue, 26 Jan 2010 15:23:18 +0000 [thread overview]
Message-ID: <4B5F08E6.9030301@carallon.com> (raw)
In-Reply-To: <hi5mi4$ngt$1@ger.gmane.org>
On 07/01/2010 22:17, Grant Edwards wrote:
> On 2010-01-07, Grant Edwards<grant.b.edwards@gmail.com> wrote:
>
>
>> The build of uboot's fw_env target tool is failing because
>> there is no mtd/mtd-user.h file.
>>
> Manually copying the mtd directory from the kernel headers into
> the toolchain /usr/include directory allows mtd stuff to build.
> I don't know how to get buildroot to do that when it's building
> a toolchain.
>
>
Rather belatedly I realise that I am seeing the same problem. When the
kernel headers are installed I get mtd-user.h in
toolchain/linux/include. Also when I build mtd-utils the header is in
build/mtd_orig/include. However it does not get copied in
staging/usr/include so any apps I write that use the header fail to compile.
I have previously fixed this my adding a rule that copies the headers
from build/mtd_orig/include when the mtd package is built.
Is this a good way to do this? Why aren't all the kernel headers made
available in staging/usr/include? How would anyone else fix this?
Thanks
Will
next prev parent reply other threads:[~2010-01-26 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 17:26 [Buildroot] Where is mtd/mtd-user.h supposed to come from? Grant Edwards
2010-01-07 22:17 ` Grant Edwards
2010-01-26 15:23 ` Will Wagner [this message]
2010-01-26 16:49 ` Grant Edwards
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=4B5F08E6.9030301@carallon.com \
--to=will_wagner@carallon.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.