[oe] [RFC][PATCH] meta-toolchain: use MULTIMACH_TARGET_SYS instead of TARGET_SYS

[Tom Rini]

On Mon, 2010-04-26 at 14:03 -0400, Denys Dmytriyenko wrote:
> On Sat, Apr 24, 2010 at 11:51:09AM -0700, Tom Rini wrote:
[snip] 
> > Right.  I'm saying that SDKPATH should be more than /usr/local/${DISTRO}
> > but /usr/local/${DISTRO}/${MACHINE} by default, toss a comment above
> > about why (output is very MACHINE specific in certain cases) and maybe
> > update the default TOOLCHAIN_OUTPUTNAME too.
> 
> Ok, you asked for a comment, I'll give you two :)
> 
> 1. In Arago I have a way to overwrite SDKPATH from the command line when 
> building a specific SDK/toolchain. So, I can do what you suggest, but...
> 
> 2. My SDKs are currently not machine-specific, moreover, they don't have the 
> cross-compile tools in them (i.e. no toolchain part), as Arago uses external 
> CodeSourcery toolchain for that. The only cross-tools I have in my SDKs are 
> those, which are missing from CS - i.e. libtool, pkgconfig, opkg, qt4e-tools 
> etc. But I still build 2 versions of SDK - armv5te and armv7a.

I'd make a very small wager that you're unknowningly wrong about #2 or a
someone adding an RRECOMMENDS/RDEPENDS_mach somewhere (or using another
machine you haven't tried yet) from machine specific stuff leaking in
and being wrong :)

It's not the gcc & co that you get from CodeSourcery or our -sdk recipes
or whatever that makes this machine-specific but the conditional
inclusion of some userland bits (be it "small" "regular" Linux stuff or
"small" stuff for FPGAs or whatever on a particular ref board).  Or even
PACKAGE_ARCH=MACHINE stuff already being in there, again without you
knowning (some of which can be rather easily pulled out with that
removal hook you added).

-- 
Tom Rini <tom_rini at mentor.com>
Mentor Graphics Corporation