From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot: could not cross-compile u-boot tools
Date: Fri, 28 Feb 2014 09:20:48 -0500 [thread overview]
Message-ID: <20140228142048.GP16805@bill-the-cat> (raw)
In-Reply-To: <20140228111231.39229380BF4@gemini.denx.de>
On Fri, Feb 28, 2014 at 12:12:31PM +0100, Wolfgang Denk wrote:
> Dear Heiko & Masahiro,
>
> In message <53105765.3010709@denx.de> you wrote:
> >
> > > 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!
>
> I'm not really hapy with the additional CROSS_BUILD_TOOLS paramert -
> but this may be a matter of taste, so the following is just a thought
> and a question:
>
> Would it make more sense to provide a sparate make target instead?
>
> Say, something like this:
>
> Build tools for host
> make CROSS_COMPILE=<your_gcc_prefix tools
> Build tools for target
> make CROSS_COMPILE=<your_gcc_prefix cross_tools
>
> ?
I agree, this seems more natural.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140228/9fa31ae4/attachment.pgp>
prev parent reply other threads:[~2014-02-28 14:20 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
2014-02-28 11:12 ` Wolfgang Denk
2014-02-28 14:20 ` Tom Rini [this message]
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=20140228142048.GP16805@bill-the-cat \
--to=trini@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