* [U-Boot] Building fw_printenv (e.g. make env) failing
@ 2014-11-02 1:46 Marcel Ziswiler
2014-11-02 10:05 ` Jeroen Hofstee
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Ziswiler @ 2014-11-02 1:46 UTC (permalink / raw)
To: u-boot
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?
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot] Building fw_printenv (e.g. make env) failing
2014-11-02 1:46 [U-Boot] Building fw_printenv (e.g. make env) failing Marcel Ziswiler
@ 2014-11-02 10:05 ` Jeroen Hofstee
2014-11-04 16:00 ` Tom Rini
0 siblings, 1 reply; 3+ messages in thread
From: Jeroen Hofstee @ 2014-11-02 10:05 UTC (permalink / raw)
To: u-boot
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot] Building fw_printenv (e.g. make env) failing
2014-11-02 10:05 ` Jeroen Hofstee
@ 2014-11-04 16:00 ` Tom Rini
0 siblings, 0 replies; 3+ messages in thread
From: Tom Rini @ 2014-11-04 16:00 UTC (permalink / raw)
To: u-boot
On Sun, Nov 02, 2014 at 11:05:04AM +0100, Jeroen Hofstee wrote:
> 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.
Yes. I forget if I spelled this out in the release notes but now that
we support CONFIG_LOCALVERSION we cannot build tools without a valid
config. For distro build support doing a "make sandbox_config ; make
env" will be a valid thing to do for some far'ish time back as well.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141104/675e9c45/attachment.pgp>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-11-04 16:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-02 1:46 [U-Boot] Building fw_printenv (e.g. make env) failing Marcel Ziswiler
2014-11-02 10:05 ` Jeroen Hofstee
2014-11-04 16:00 ` Tom Rini
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox