Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Thiemo Seufer <ths@networkno.de>
Cc: Tim Bird <tim.bird@am.sony.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH] fix mips/Makefile to support CROSS_COMPILE from environment var
Date: Thu, 4 May 2006 14:04:49 -0700	[thread overview]
Message-ID: <20060504210449.GA12676@smtp.west.cox.net> (raw)
In-Reply-To: <20060504205517.GF18218@networkno.de>

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/

  reply	other threads:[~2006-05-04 21:05 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 [this message]
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
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=20060504210449.GA12676@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ths@networkno.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox