All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] fix mips/Makefile to support CROSS_COMPILE from environment var
Date: Thu, 4 May 2006 23:35:39 +0100	[thread overview]
Message-ID: <20060504223539.GG18218@networkno.de> (raw)
In-Reply-To: <445A6F51.90308@am.sony.com>

Tim Bird wrote:
> Thiemo Seufer wrote:
> > It looks like the other arch-specific Makefiles also override the
> > environment.
> 
> 4 other arches I work with don't.
> 
> > To work around the problem, you can disable
> > CONFIG_CROSSCOMPILE and define CROSS_COMPILE in the environment.
> 
> I thought that might be the case, but that's pretty broken IMHO.
> It's counterintuitive and undocumented.
> 
> > 
> > Strangely enough, the help for CONFIG_CROSSCOMPILE already explains
> > that.
> 
> Here's the help from my Kconfig.debug:
> 
>           Say Y here if you are compiling the kernel on a different
>           architecture than the one it is intended to run on.
> 
> Am I missing something?

Update to a newer version:

config CROSSCOMPILE
	bool "Are you using a crosscompiler"
	help
	  Say Y here if you are compiling the kernel on a different
	  architecture than the one it is intended to run on.  This is just a
	  convenience option which will select the appropriate value for
	  the CROSS_COMPILE make variable which otherwise has to be passed on
	  the command line from mips-linux-, mipsel-linux-, mips64-linux- and
	  mips64el-linux- as appropriate for a particular kernel configuration.
	  You will have to pass the value for CROSS_COMPILE manually if the
	  name prefix for your tools is different.


Thiemo

  reply	other threads:[~2006-05-04 22:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 19:35 [PATCH] fix mips/Makefile to support CROSS_COMPILE from environment var Tim Bird
2006-05-04 20:55 ` Thiemo Seufer
2006-05-04 21:04   ` Tom Rini
2006-05-04 21:25     ` Kevin D. Kissell
2006-05-04 21:25       ` Kevin D. Kissell
2006-05-04 21:32       ` Kevin D. Kissell
2006-05-04 21:32         ` Kevin D. Kissell
2006-05-04 21:44       ` Tom Rini
2006-05-04 23:06     ` Ralf Baechle
2006-05-04 23:14       ` Tom Rini
2006-05-04 23:34         ` Tom Rini
2006-05-05  7:45           ` Geert Uytterhoeven
2006-05-05 18:45             ` Wolfgang Denk
2006-05-08 18:35       ` [PATCH] fix mips/Makefile to support CROSS_COMPILE from envir onment var Tim Bird
2006-05-08 18:56         ` Dan Malek
2006-05-04 21:17   ` [PATCH] fix mips/Makefile to support CROSS_COMPILE from environment var Tim Bird
2006-05-04 22:35     ` Thiemo Seufer [this message]
2006-05-08 18:22       ` Tim Bird

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=20060504223539.GG18218@networkno.de \
    --to=ths@networkno.de \
    --cc=linux-mips@linux-mips.org \
    --cc=tim.bird@am.sony.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.