From: Ralf Baechle <ralf@linux-mips.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Thiemo Seufer <ths@networkno.de>, 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: Fri, 5 May 2006 00:06:47 +0100 [thread overview]
Message-ID: <20060504230647.GA3465@linux-mips.org> (raw)
In-Reply-To: <20060504210449.GA12676@smtp.west.cox.net>
On Thu, May 04, 2006 at 02:04:49PM -0700, Tom Rini wrote:
> 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.
Having such information in an environment variable is imho terribly
inelegant, having to pass it on the command line for each make invocation
is terrible abuse for the fingertips so I went for this option which makes
the makefile pick the right prefix.
Ralf
next prev parent reply other threads:[~2006-05-04 23:06 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 [this message]
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=20060504230647.GA3465@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=ths@networkno.de \
--cc=tim.bird@am.sony.com \
--cc=trini@kernel.crashing.org \
/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.