Dear Mike Frysinger, In message <201110181614.46289.vap...@gentoo.org> you wrote: > > > 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. > > my proposal is only for the default behavior, and it only searches $PATH. if > the auto-lookup isn't what the user wants, they still can set CROSS_COMPILE= > themselves. so all existing usage is unchanged.
While we are at it I would like to fix the known (to me) problems of the current usage - that is for example that ARCH=arm includes for example both little and big endian systems, which usually require different tool chains to be used. > to add a further bit of flexibility, i might also propose that MAKEALL check > the variable CROSS_COMPILE_<arch> and automatically set CROSS_COMPILE to that > before running `make`. this way people can do CROSS_COMPILE_arm=... > CROSS_COMPILE_powerpc=... ./MAKEALL arm powerpc. 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. 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 In my experience the best way to get something done is to give it to someone who is busy. - Terry Pratchett, _Going_Postal_ _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
