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@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
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
