linux-mips
[Top] [All Lists]

Re: MIPS Makefile not picking up CROSS_COMPILE from environment setting

To: Wolfgang Denk <wd@denx.de>
Subject: Re: MIPS Makefile not picking up CROSS_COMPILE from environment setting
From: Ralf Baechle <ralf@linux-mips.org>
Date: Fri, 19 Oct 2007 12:18:23 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <20071018184636.48637242E9@gemini.denx.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20071018184636.48637242E9@gemini.denx.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.14 (2007-02-12)
On Thu, Oct 18, 2007 at 08:46:36PM +0200, Wolfgang Denk wrote:

> I noticed that, unlike for other architectures like ARM  or  PowerPC,
> the  MIPS Makefile does not pick up the settings from a CROSS_COMPILE
> environment variable, at least not with many (all?) default  configu-
> rations.
> 
> This makes no sense to me - is there an intention behind it?

There are four different tool prefixes possible for MIPS kernels,
mips-linux-, mipsel-linux-, mips64-linux- and mips64el-linux.  This bit
in the Makefile makes the kernel automatically pick up the right thing
if CONFIG_CROSSCOMPILE is set.

The idea of passing CROSS_COMPILE from the environment always seemed to
be wrong to me - I keep jumping between all sorts of weird different
kernel configurations so no single setting of an environment variable
would cut it.

What I'd really like to see is a properly working CONFIG_MYARCH option
selectable in Kconfig.  Then the makefiles should figure out if it's a
native or crosscompile and add the right tool prefix.  The user should
not need to know that sort of stuff unless he wants to.

  Ralf

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