public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot: could not cross-compile u-boot tools
Date: Fri, 28 Feb 2014 10:31:17 +0100	[thread overview]
Message-ID: <53105765.3010709@denx.de> (raw)
In-Reply-To: <20140228180259.94F3.AA925319@jp.panasonic.com>

Hallo Masahiro,

Am 28.02.2014 10:03, schrieb Masahiro Yamada:
> Hello Heiko,
>
>>>> Is this a Bug, which should be fixed? Any hints?
>>>
>>> It seems like we need to pick up
>>> http://lists.linaro.org/pipermail/linaro-kernel/2013-August/005772.html
>>
>> Yes, this seems a way to go...
>>
>> @Masahiro: What is your opinion?
>
> Hmm, I don't like such a patch because
>   [1] It changes too much

Ok, if there is an easier way, that would be great!

>   [2] We must build tools in two steps.
>      First time, build tools for host
>            make O=path/to/buildhost/ silentoldconfig prepare scripts
>      Second time, built tools for the target
>       make HOSTCC=$CROSS_COMPILE \
>             KBUILD_SCRIPTROOT=path/to/buildhost/
>              silentoldconfig prepare scripts
>     It seems ridiculous to type so many magic commands.

But it should be possible to compile the "tools" for the
target. If this a serperate build step, that is as it was
before the kbuild changes, so that should be no problem.

> Heiko, can you check if the following works for you?
>
>
> Modify tools/Makefile as follows
>
>    --- a/tools/Makefile
>    +++ b/tools/Makefile
>    @@ -5,6 +5,10 @@
>     # SPDX-License-Identifier:     GPL-2.0+
>     #
>
>     +ifneq ($(CROSS_BUILD_TOOLS),)
>     +HOSTCC = $(CC)
>     +endif
>     +
>      #
>      # toolchains targeting win32 generate .exe files
>      #
>
>
> Usage:
> Build tools for host
>       make  CROSS_COMPILE=<your_gcc_prefix>  tools
> Build tools for target
>       make CROSS_BUILD_TOOLS=1  CROSS_COMPILE=<your_gcc_prefix>  tools

Yep, works, great!

> This is my log.
>
> $ make IDS8247_config
[...]
> $ file tools/mkimage
> tools/mkimage: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0xb76ad5a10a41700fcab9e86c079118c424446d89, with unknown capability 0x41000000 = 0xf676e75, with unknown capability 0x10000 = 0x70401, not stripped
>
>
>
> Uknown Issue:
> Tools are not stripped.
> Too big for your target board?

strip them would be nice ...

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2014-02-28  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140227204101.77B6.AA925319@jp.panasonic.com>
     [not found] ` <530F2804.4020107@denx.de>
     [not found]   ` <20140227210758.77BA.AA925319@jp.panasonic.com>
2014-02-27 12:20     ` [U-Boot] U-Boot: could not cross-compile u-boot tools Heiko Schocher
2014-02-27 14:30       ` Tom Rini
2014-02-28  5:21         ` Heiko Schocher
2014-02-28  9:03           ` Masahiro Yamada
2014-02-28  9:31             ` Heiko Schocher [this message]
2014-02-28 11:12               ` Wolfgang Denk
2014-02-28 14:20                 ` 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=53105765.3010709@denx.de \
    --to=hs@denx.de \
    --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