Dear Mike Frysinger,
In message <201110181301.57390.vap...@gentoo.org> you wrote:
>
> because MAKEALL is a pita to use. it has no automatic CROSS_COMPILE support,
> and the current logic only allows one-CROSS_COMPILE-setting-per-run. so you
> have to run MAKEALL by hand once per arch.
>
> the documentation you quote only shows running MAKEALL for powerpc (since
> that's the default), so even the docs are a bit unclear.
>
> ideally, MAKEALL should be intelligent and automatically find an appropriate
> toolchain if one isn't setup in the env. much like the buildall script i
> posted recently.
How is this supposed to work? Assume I have a number of different
tool chains, say I want to use the tool chain in /opt/eldk-5.1/armv5te
for all ARM9 systems, that in /opt/eldk-5.1/armv7a for all OMAP based
boards, that in /opt/eldk-5.1/armv6 for Kirkwood processors and yet
another one for the (bix endian) PXA boards. In all cases we have
ARCH=arm and CROSS_COMPILE=arm-linux-gnueabi-
And then, for compatibility testings, I want to compile all this with
ELDK 4.2. Or ELDK 4.1. Or CodeSourcery xxx. Or...
I see no clean way to implement this - ok, we could provide an
external tool / data base that maps boards or SoC names to
CROSS_COMPILE/ARCH/PATH settings, which each user has to configure for
his own set of tool chain settings.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
Those who hate and fight must stop themselves -- otherwise it is not
stopped.
-- Spock, "Day of the Dove", stardate unknown
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
