From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Tue, 18 Oct 2011 18:18:07 -0400 Subject: [U-Boot] MAKEALL In-Reply-To: <20111018215052.84F29140877D@gemini.denx.de> References: <20111018062310.61320140797D@gemini.denx.de> <201110181655.29507.vapier@gentoo.org> <20111018215052.84F29140877D@gemini.denx.de> Message-ID: <201110181818.08674.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tuesday 18 October 2011 17:50:52 Wolfgang Denk wrote: > Mike Frysinger wrote: > > > That would still be to coarse for above issue. Also, you might want > > > to use different ARM tool chains for ARMv5te systemd than for ARMv6 > > > and yet other ones for ARMv7a, etc. > > > > the idea is easy to extend to CROSS_COMPILE_ and perhaps even > > CROSS_COMPILE_ > > The problem is that this does not differentiate the tool chains. > > CROSS_COMPILE would be arm-linux-gnueabi- in all these cases - it's > PATH that needs to be different in my case. or a full path to the toolchain base: CROSS_COMPILE=/path/to/foo/arm-linux-gnueabi- > Eventually we should not try to catch all situations directly, but allow for > a soc|cpu|vendor|board|whatever specific file name to be sourced by the > script, which then would be responsible to set up the environment as > needed? toolchains tend to be site-specific. i use compilers i created myself, or found via kernel.org, or i've gotten directly from SoC vendors. all of which have different names. so while i think it'd be fine for maintainers to specify a preference, it would merely be that. -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/20111018/2152920f/attachment.pgp