From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building fw_printenv (e.g. make env) failing
Date: Sun, 02 Nov 2014 11:05:04 +0100 [thread overview]
Message-ID: <545601D0.4000605@myspectrum.nl> (raw)
In-Reply-To: <1414892811.2407.12.camel@localhost.localdomain>
Hello Marcel,
On 02-11-14 02:46, Marcel Ziswiler wrote:
> Quick question: How does one actually go about building fw_printenv
> nowadays? At lest just doing 'make env' fails for me:
>
> [user at host u-boot.git]$ make env
> HOSTCC tools/env/aes.o
> HOSTCC tools/env/crc32.o
> HOSTCC tools/env/ctype.o
> HOSTCC tools/env/env_attr.o
> HOSTCC tools/env/env_flags.o
> HOSTCC tools/env/fw_env.o
> In file included from tools/env/fw_env.c:117:0:
> include/env_default.h:110:11: error: expected ?}? before
> ?CONFIG_SYS_ARCH?
> make[1]: *** [tools/env/fw_env.o] Error 1
> make: *** [env] Error 2
>
> I suspect some generated/autoconf.h discrepancy but am unsure how to
> properly fix that. Any suggestions?
>
>
make sandbox_config
make env
Should do the job.
Regards,
Jeroen
next prev parent reply other threads:[~2014-11-02 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 1:46 [U-Boot] Building fw_printenv (e.g. make env) failing Marcel Ziswiler
2014-11-02 10:05 ` Jeroen Hofstee [this message]
2014-11-04 16:00 ` Tom Rini
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=545601D0.4000605@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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