From: Grant Edwards <grant.b.edwards@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [WIP] tools/env: cleanup host build flags
Date: Wed, 10 Nov 2010 22:12:51 +0000 (UTC) [thread overview]
Message-ID: <ibf5d2$orb$1@dough.gmane.org> (raw)
In-Reply-To: 20101110200048.9D3151522C0@gemini.denx.de
On 2010-11-10, Wolfgang Denk <wd@denx.de> wrote:
> Dear Mike Frysinger,
>
> In message <201011100423.13449.vapier@gentoo.org> you wrote:
>>
>> > - use the cross compiler again (fw_printenv is intended for a
>> > hosted environment on the target).
>>
>> the cross-compiler used to create u-boot has no guarantee that it'll produce
>> executables useful for the target OS. often this isnt the case. HOSTCC
>
> Really? You mean, you need different tool chains to build U-Boot, the
> Linux kernel or user space applications? Frankly, I consider those
> tool chains broken.
Sounds like somethings broken to me as well. I've always used the same
toolchain for U-Boot, Kernel, Atmel bootstrap, and user-space stuff
(vis buildroot).
The only think I use a separate toolchain for are Atmel's "applets"
that are part of the SAM-BA utility -- and that's only because I'm too
lazy to fix Atmel's Makefiles so they call the compiler with the
proper flags.
--
Grant Edwards grant.b.edwards Yow! Are we THERE yet?
at
gmail.com
prev parent reply other threads:[~2010-11-10 22:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 16:06 [U-Boot] [WIP] tools/env: cleanup host build flags Daniel Hobi
2010-10-11 19:16 ` Scott Wood
2010-11-09 15:03 ` Detlev Zundel
2010-11-09 15:58 ` Steve Sakoman
2010-11-10 9:23 ` Mike Frysinger
2010-11-10 11:58 ` Daniel Hobi
2010-11-10 22:09 ` Mike Frysinger
2010-11-10 13:11 ` [U-Boot] [PATCH] " Daniel Hobi
2010-11-10 20:00 ` [U-Boot] [WIP] " Wolfgang Denk
2010-11-10 22:06 ` Mike Frysinger
2010-11-10 22:25 ` Wolfgang Denk
2010-11-10 22:51 ` Mike Frysinger
2010-11-10 22:12 ` Grant Edwards [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='ibf5d2$orb$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.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