From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] problem building fw_printenv
Date: Thu, 10 Dec 2009 17:45:29 -0600 [thread overview]
Message-ID: <4B218819.3090909@freescale.com> (raw)
In-Reply-To: <20091210232901.CCDDF19F3F@gemini.denx.de>
Wolfgang Denk wrote:
>> fw_env.c:43:27: error: mtd/mtd-user.h: No such file or directory
>>
>> So then, I have this problem with mtd-user.h not being found. If I
>> define MTD_VERSION=old, it then uses mtd.h and gets further but
>> encounters another error within mtd.h.
>
> There will probably more problems to follow...
>
>> Seems like I shouldn't have to define MTD_VERSION=old in the first
>> place, but without it no mtd-user.h file. Any more suggestions?
>
> Try a sane build environment?
I have the same problems building this. We need to define phys_addr_t
somewhere if we're going to include u-boot internal headers in a user tool.
-Scott
next prev parent reply other threads:[~2009-12-10 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 0:38 [U-Boot] problem building fw_printenv twebb
2009-12-10 20:18 ` twebb
2009-12-10 20:34 ` Jerry Van Baren
2009-12-10 20:39 ` Scott Wood
2009-12-10 21:20 ` twebb
2009-12-10 23:29 ` Wolfgang Denk
2009-12-10 23:45 ` Scott Wood [this message]
2010-01-18 10:31 ` Kári Davíðsson
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=4B218819.3090909@freescale.com \
--to=scottwood@freescale.com \
--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 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.