Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Wolfgang Denk <wd@denx.de>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS Makefile not picking up CROSS_COMPILE from environment setting
Date: Fri, 19 Oct 2007 12:18:23 +0100	[thread overview]
Message-ID: <20071019111823.GB30767@linux-mips.org> (raw)
In-Reply-To: <20071018184636.48637242E9@gemini.denx.de>

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

  parent reply	other threads:[~2007-10-19 11:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 18:46 MIPS Makefile not picking up CROSS_COMPILE from environment setting Wolfgang Denk
2007-10-19  2:47 ` Atsushi Nemoto
2007-10-19  7:16 ` Geert Uytterhoeven
2007-10-21  8:37   ` Geert Uytterhoeven
2007-10-22 13:21     ` Ralf Baechle
2007-10-22 14:30       ` Geert Uytterhoeven
2007-10-19 11:18 ` Ralf Baechle [this message]
2007-10-19 12:39   ` Maciej W. Rozycki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071019111823.GB30767@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=wd@denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox