On Thu, May 04, 2006 at 09:55:17PM +0100, Thiemo Seufer wrote: > Tim Bird wrote: > > The following patch allows to build using CROSS_COMPILE from the environment. > > I have an automated system which works like this, but it chokes on MIPS when > > I use it with (albeit non-standard-named) cross-compiler tools. An easy > > workaround I'm using is to put CROSS_COMPILE on the make command line, but it would > > be nice to use the definition already in the environment when I work > > manually in the system. > > > > For past discussion of this see: > > http://www.linux-mips.org/archives/linux-mips/2003-02/msg00196.html > > > > I'm not sure why the change didn't make it in back in 2003, but > > if the complaint was about the use of "?=", that seems to be in use > > other places, and fairly standard now. > > > > For example, from the top level kernel Makefile: > > ARCH ?= $(SUBARCH) > > CROSS_COMPILE ?= > > It looks like the other arch-specific Makefiles also override the > environment. To work around the problem, you can disable > CONFIG_CROSSCOMPILE and define CROSS_COMPILE in the environment. > > Strangely enough, the help for CONFIG_CROSSCOMPILE already explains > that. Let me ask a stupid question. With all of the ways to otherwise do a cross compile, why a config option on MIPS? ARM*/SH*, which are at least as likely to not be native-compiled, don't do that. Just something I've always wondered, really. -- Tom Rini http://gate.crashing.org/~trini/
