Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Where is mtd/mtd-user.h supposed to come from?
Date: Thu, 7 Jan 2010 22:17:40 +0000 (UTC)	[thread overview]
Message-ID: <hi5mi4$ngt$1@ger.gmane.org> (raw)
In-Reply-To: hi55gi$ol6$1@ger.gmane.org

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.

Though the mtd programs build, they still wonn't run, since
libgcc_s is missing, but more on that in another thread...

-- 
Grant Edwards                   grante             Yow! PUNK ROCK!!  DISCO
                                  at               DUCK!!  BIRTH CONTROL!!
                               visi.com            

  reply	other threads:[~2010-01-07 22:17 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 [this message]
2010-01-26 15:23   ` Will Wagner
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='hi5mi4$ngt$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox