linux-mips
[Top] [All Lists]

Re: [PATCH] fix mips/Makefile to support CROSS_COMPILE from environment

To: Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH] fix mips/Makefile to support CROSS_COMPILE from environment var
From: Thiemo Seufer <ths@networkno.de>
Date: Thu, 4 May 2006 21:55:17 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <445A577D.7090507@am.sony.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <445A577D.7090507@am.sony.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.11+cvs20060403
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.


Thiemo

<Prev in Thread] Current Thread [Next in Thread>