public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Loïc Minier" <lool@dooz.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] kfreebsd build failure - fw_env.c:43:27: error: mtd/mtd-user.h: No such file or directory
Date: Mon, 7 Feb 2011 23:23:31 +0100	[thread overview]
Message-ID: <20110207222331.GD5848@bee.dooz.org> (raw)
In-Reply-To: <20110207220605.AD62F14B4BD5@gemini.denx.de>

On Mon, Feb 07, 2011, Wolfgang Denk wrote:
> >  If not, I guess this should be removed from tools-all is mtd/mtd-user.h
> >  isn't found; is there any recommendation in doing this?
> Even if you are building in a *BSD environment, you could still be
> building for a Linux target system. After all, the fw_env.* tools are
> target tools, which should not depend on the host environment.

 Yes; I mean if this target header is not found (if you're
 cross-building, you should have the headers for your target)


 (BTW, some tools are kind of both host and target tools, like mkimage
 which might be used during the build but are also interesting to build
 for the target architecture.  Ideally when cross-compiling these should
 be built twice, but I realize it's a pain to implement)

-- 
Lo?c Minier

  reply	other threads:[~2011-02-07 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 21:09 [U-Boot] kfreebsd build failure - fw_env.c:43:27: error: mtd/mtd-user.h: No such file or directory Loïc Minier
2011-02-07 22:06 ` Wolfgang Denk
2011-02-07 22:23   ` Loïc Minier [this message]
2011-02-07 23:23   ` [U-Boot] [PATCH] Only build fw_printenv if we have mtd/mtd-user.h Loïc Minier
2011-04-12 19:27     ` Wolfgang Denk
2011-04-12 19:46       ` Loïc Minier

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=20110207222331.GD5848@bee.dooz.org \
    --to=lool@dooz.org \
    --cc=u-boot@lists.denx.de \
    /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