On Wed, Jan 15, 2014 at 11:23 +0900, Masahiro Yamada wrote:
I did not know how env target have been used.
Your comments are highly appreciated!
I will revive env target at v5.
But whan I cannot understand is why HOSTCC must be tweaked.
(I am also asking this question in Compiling
Hello Gerhard.
There is another issue for those who do
make HOSTCC=${CROSS_COMPILE}gcc env
(needs a HOSTSTRIP spec as well in recent mainline sources)
to get an fw_printenv(1) binary that runs on the target (in
contrast to the build machine). Some yocto recipes do this, to
not
On Fri, Jan 10, 2014 at 15:44 +0900, Masahiro Yamada wrote:
- Move easylogo, env, gdb tagets to tools/Makefile
- Delete gdbtools target (same as gdb)
This appears to be an incompatible change with regards to how
users can compile these tools. Please see tools/env/README and
update it as
- Move easylogo, env, gdb tagets to tools/Makefile
- Delete gdbtools target (same as gdb)
Signed-off-by: Masahiro Yamada yamad...@jp.panasonic.com
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
Makefile | 7 +--
tools/Makefile | 6 +-
2 files changed, 6
4 matches
Mail list logo
