From: "Kevin D. Kissell" <kevink@mips.com>
To: "Kevin D. Kissell" <kevink@mips.com>,
"Tom Rini" <trini@kernel.crashing.org>,
"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 23:32:29 +0200 [thread overview]
Message-ID: <028901c66fc2$3ff139f0$10eca8c0@grendel> (raw)
In-Reply-To: 028201c66fc1$4f724d20$10eca8c0@grendel
> > 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.
>
> Probably because, unlike ARM and SH, the MIPS architecture began life
> as a workstation/server processor, and for a while there cross-compilation
> was the exception rather than the rule.
Before anyone else jumps in, yeah, ARM was sort-of a workstation processor
to begin with, too, but I don't think the original Acorn RISC Machine was set
up to run a "real" OS, with memory management, etc., whereas MIPS was.
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Kevin D. Kissell" <kevink@mips.com>,
Tom Rini <trini@kernel.crashing.org>,
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 23:32:29 +0200 [thread overview]
Message-ID: <028901c66fc2$3ff139f0$10eca8c0@grendel> (raw)
Message-ID: <20060504213229.7L110evKL87LW6rERuTh-wDpOeskS3OEejtS1Kcjiio@z> (raw)
In-Reply-To: 028201c66fc1$4f724d20$10eca8c0@grendel
> > 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.
>
> Probably because, unlike ARM and SH, the MIPS architecture began life
> as a workstation/server processor, and for a while there cross-compilation
> was the exception rather than the rule.
Before anyone else jumps in, yeah, ARM was sort-of a workstation processor
to begin with, too, but I don't think the original Acorn RISC Machine was set
up to run a "real" OS, with memory management, etc., whereas MIPS was.
Regards,
Kevin K.
next prev parent reply other threads:[~2006-05-04 21:29 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 [this message]
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='028901c66fc2$3ff139f0$10eca8c0@grendel' \
--to=kevink@mips.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox