From: Denys Dmytriyenko <denys@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building fw_env tools seems broken
Date: Tue, 2 Dec 2014 13:09:11 -0500 [thread overview]
Message-ID: <20141202180911.GF5113@edge> (raw)
In-Reply-To: <20141124211917.GC2242@edge>
Ping on this one.
I tried few different defconfigs - the results are mixed, where sandbox and
some other machines do work, but some are broken as below. Tried different
toolchains as well - gcc-4.7 and 4.9. Any pointers or any help in resolving
this issue would be greatly appreciated! Thanks.
On Mon, Nov 24, 2014 at 04:19:17PM -0500, Denys Dmytriyenko wrote:
> Hi,
>
> I came across this issue recently, that affects 2014.10 as well as master, but
> used to work fine in 2014.07 and older. Please let me know if I'm missing
> something or you need additional info. Thanks!
>
>
> $ make CROSS_COMPILE=arm-linux-gnueabihf- am335x_evm_defconfig
> HOSTCC scripts/basic/fixdep
> HOSTCC scripts/kconfig/conf.o
> HOSTCC scripts/kconfig/zconf.tab.o
> HOSTLD scripts/kconfig/conf
> #
> # configuration written to .config
> #
> #
> # configuration written to spl/.config
> #
>
> $ make CROSS_COMPILE=arm-linux-gnueabihf- env
> scripts/kconfig/conf --silentoldconfig Kconfig
> scripts/kconfig/conf --silentoldconfig Kconfig
> CHK include/config.h
> GEN include/autoconf.mk
> GEN include/autoconf.mk.dep
> GEN spl/include/autoconf.mk
> 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?
> scripts/Makefile.host:108: recipe for target 'tools/env/fw_env.o' failed
> make[1]: *** [tools/env/fw_env.o] Error 1
> Makefile:1208: recipe for target 'env' failed
> make: *** [env] Error 2
>
> --
> Denys
next prev parent reply other threads:[~2014-12-02 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 21:19 [U-Boot] Building fw_env tools seems broken Denys Dmytriyenko
2014-12-02 18:09 ` Denys Dmytriyenko [this message]
2014-12-03 1:28 ` Masahiro Yamada
2014-12-03 16:33 ` Denys Dmytriyenko
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=20141202180911.GF5113@edge \
--to=denys@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox