From: "H. Peter Anvin" <hpa@zytor.com>
To: Thorsten Glaser <t.glaser@tarent.de>,
Richard Weinberger <richard@nod.at>
Cc: linux-arch@vger.kernel.org, mmarek@suse.cz, geert@linux-m68k.org,
ralf@linux-mips.org, lethal@linux-sh.org, jdike@addtoit.com,
gxt@mprc.pku.edu.cn, tglx@linutronix.de, mingo@redhat.com,
x86@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
linux-mips@linux-mips.org, linux-sh@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [RFC] Get rid of SUBARCH
Date: Wed, 21 Aug 2013 14:58:04 +0200 [thread overview]
Message-ID: <7813eeb3-8f96-4d3d-87ec-f2a880122804@email.android.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1308211452260.31430@tglase.lan.tarent.de>
If ARCH doesn't match uname for some definition of match?
Thorsten Glaser <t.glaser@tarent.de> wrote:
>On Wed, 21 Aug 2013, Richard Weinberger wrote:
>
>> The series touches also m68k, sh, mips and unicore32.
>> These architectures magically select a cross compiler if ARCH !=
>SUBARCH.
>> Do really need that behavior?
>
>Not precisely that, but it’s very common in m68k land
>to just cross-build kernels with
>
>$ make ARCH=m68k menuconfig
>$ make ARCH=m68k
>
>Maybe a generalising of that feature, and making it
>independent of SUBARCH (which can then die)?
>
>bye,
>//mirabilos
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
prev parent reply other threads:[~2013-08-21 12:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 8:19 [RFC] Get rid of SUBARCH Richard Weinberger
2013-08-21 8:19 ` [PATCH 1/8] um: Create defconfigs for i386 and x86_64 Richard Weinberger
2013-08-22 4:55 ` Stephen Rothwell
2013-09-26 10:20 ` Ramkumar Ramachandra
2013-09-26 10:35 ` Richard Weinberger
2013-09-26 11:57 ` Ramkumar Ramachandra
2013-09-26 12:04 ` Richard Weinberger
2013-09-27 9:22 ` Toralf Förster
2013-09-27 9:26 ` Richard Weinberger
2013-08-21 8:19 ` [PATCH 2/8] um: Do not use SUBARCH Richard Weinberger
2013-09-26 10:40 ` Ramkumar Ramachandra
2013-09-26 10:44 ` Richard Weinberger
2013-09-26 10:53 ` Ramkumar Ramachandra
2013-09-26 11:01 ` Richard Weinberger
2013-09-26 11:43 ` Ramkumar Ramachandra
2013-09-26 11:56 ` Richard Weinberger
2013-09-26 12:00 ` Ramkumar Ramachandra
2013-09-26 13:13 ` Ramkumar Ramachandra
2013-09-26 13:26 ` Geert Uytterhoeven
2013-09-26 13:56 ` Richard Weinberger
2013-09-26 13:57 ` Ramkumar Ramachandra
2013-09-26 14:24 ` Richard Weinberger
2013-09-26 14:36 ` Ramkumar Ramachandra
2013-09-26 15:04 ` Richard Weinberger
2013-09-26 16:06 ` Ramkumar Ramachandra
2013-09-26 17:10 ` Richard Weinberger
2013-08-21 8:19 ` [PATCH 3/8] um: Remove old defconfig Richard Weinberger
2013-08-21 8:19 ` [PATCH 4/8] m68k: Do not use SUBARCH Richard Weinberger
2013-08-21 8:19 ` [PATCH 5/8] sh: " Richard Weinberger
2013-08-21 8:19 ` [PATCH 6/8] mips: " Richard Weinberger
2013-08-21 8:19 ` [PATCH 7/8] unicore32: " Richard Weinberger
2013-08-21 8:19 ` [PATCH 8/8] Makefile: Remove SUBARCH Richard Weinberger
2013-08-21 12:07 ` [RFC] Get rid of SUBARCH Geert Uytterhoeven
2013-08-21 12:16 ` Richard Weinberger
2013-08-21 17:25 ` Rob Landley
2013-08-21 19:51 ` Sam Ravnborg
2013-08-22 12:58 ` Geert Uytterhoeven
2013-08-22 20:41 ` Rob Landley
2013-08-22 20:55 ` David Daney
2013-08-22 21:32 ` Rob Landley
2013-08-21 12:53 ` Thorsten Glaser
2013-08-21 12:58 ` H. Peter Anvin [this message]
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=7813eeb3-8f96-4d3d-87ec-f2a880122804@email.android.com \
--to=hpa@zytor.com \
--cc=geert@linux-m68k.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=jdike@addtoit.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
--cc=t.glaser@tarent.de \
--cc=tglx@linutronix.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=x86@kernel.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