From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mike Frysinger <vapier@gentoo.org>
Date: Wed, 10 Nov 2010 17:51:51 -0500
Subject: [U-Boot] [WIP] tools/env: cleanup host build flags
In-Reply-To: <20101110222531.CF6D31522C0@gemini.denx.de>
References: <1286813206-20163-1-git-send-email-daniel.hobi@schmid-telecom.ch>
	<201011101706.17988.vapier@gentoo.org>
	<20101110222531.CF6D31522C0@gemini.denx.de>
Message-ID: <201011101751.52423.vapier@gentoo.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.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