From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [WIP] tools/env: cleanup host build flags
Date: Wed, 10 Nov 2010 17:51:51 -0500 [thread overview]
Message-ID: <201011101751.52423.vapier@gentoo.org> (raw)
In-Reply-To: <20101110222531.CF6D31522C0@gemini.denx.de>
On Wednesday, November 10, 2010 17:25:31 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > > IIRC, HOSTCC refers to the C compiler on the and for the build host,
> > > i. e. when running on a x86 system it will create x86 code. This is
> > > obviously wrong when we try to build fw_printenv for, say, a PPC4xx
> > > system.
> >
> > and it is trivial for the user to say "i wish to build tools for PPC4xx
> > userland"
>
> Is it? And how so?
i already said multiple times how to do it:
make tools env HOSTCC=bfin-uclinux-gcc
and that works for *all* tools instead of just some
> And why would this not be the default setting, then?
i already said why it doesnt make sense to assume "one toolchain fits all" and
why that requirement is fundamentally wrong. Daniel already suggested a
refinement to better control intentions which isnt fundamentally broken.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20101110/ebc8b37d/attachment.pgp
next prev parent reply other threads:[~2010-11-10 22:51 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 [this message]
2010-11-10 22:12 ` Grant Edwards
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=201011101751.52423.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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