[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7813eeb3-8f96-4d3d-87ec-f2a880122804@email.android.com>
Date: Wed, 21 Aug 2013 14:58:04 +0200
From: "H. Peter Anvin" <hpa@...or.com>
To: Thorsten Glaser <t.glaser@...ent.de>,
Richard Weinberger <richard@....at>
CC: linux-arch@...r.kernel.org, mmarek@...e.cz, geert@...ux-m68k.org,
ralf@...ux-mips.org, lethal@...ux-sh.org, jdike@...toit.com,
gxt@...c.pku.edu.cn, tglx@...utronix.de, mingo@...hat.com,
x86@...nel.org, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-m68k@...r.kernel.org,
linux-mips@...ux-mips.org, linux-sh@...r.kernel.org,
user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: [RFC] Get rid of SUBARCH
If ARCH doesn't match uname for some definition of match?
Thorsten Glaser <t.glaser@...ent.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists