From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Richard Weinberger <richard@nod.at>,
Linux-Arch <linux-arch@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>, Ralf Baechle <ralf@linux-mips.org>,
Paul Mundt <lethal@linux-sh.org>, Jeff Dike <jdike@addtoit.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [RFC] Get rid of SUBARCH
Date: Wed, 21 Aug 2013 12:25:11 -0500 [thread overview]
Message-ID: <1377105911.2737.94@driftwood> (raw)
In-Reply-To: <CAMuHMdWk-EPTNmPB1O1+F7YVQLjhQsFJznYwA3t6UCGUU1T9PQ@mail.gmail.com> (from geert@linux-m68k.org on Wed Aug 21 07:07:33 2013)
On 08/21/2013 07:07:33 AM, Geert Uytterhoeven wrote:
> On Wed, Aug 21, 2013 at 10:19 AM, Richard Weinberger <richard@nod.at>
> wrote:
> > This series is an attempt to remove the SUBARCH make parameter.
> > It as introduced at the times of Linux 2.5 for UML to tell the UML
> > build system what the real architecture is.
> >
> > But we actually don't need SUBARCH, we can store this information
> > in the .config file.
>
> Haha, now you have OS_ARCH (shouldn't that be called HOST_ARCH?)
> instead,
> which is available only for UM?
>
> > The series touches also m68k, sh, mips and unicore32.
> > These architectures magically select a cross compiler if ARCH !=
> SUBARCH.
> > Do really need that behavior?
>
> This does remove functionality.
> It allows to build a kernel using e.g. "make ARCH=m68k".
make ARCH=m68k CROSS_COMPILE=m68k-
make ARCH=arm CROSS_COMPILE=armv5l-
make ARCH=sparc CROSS_COMPILE=sparc-
make ARCH=ppc CROSS_COMPILE=powerpc-
make ARCH=sh CROSS_COMPILE=sh4-
make ARCH=mips CROSS_COMPILE=mipsel-
make ARCH=x86 CROSS_COMPILE=i686-
make ARCH=alpha CROSS_COMPILE=alpha-
Works the same way on all the targets I've tried so far. You specify
the architecture, you specify the cross compiler prefix, you feed it a
config file, you build.
(If a target supplies its own default cross compiler prefix I just have
to override it with what mine's called anyway...)
> Perhaps this can be moved to generic code? Most (not all!)
> cross-toolchains
> are called $ARCH-{unknown-,}linux{,-gnu}.
> Exceptions are e.g. am33_2.0-linux and bfin-uclinux.
The linaro toolchain is arm-linux-gnueabihf- and the one on kernel.org
is arm-unknown-linux-gnueabi- and the one I build is armv5l- (because
the FSF's
$ARCH-unknown-gnu-format-tuple-all-hail-stallman-gnu-gnu-gnu-dammit-gcc
is just nuts: why would I say -linux- in a linux-to-linux toolchain? Do
windows toolchains say -windows-?)
Other toolchain sources use other prefixes (-unknown- is often
-$VENDORNAME-), and then of course there's llvm... which is why you
specify CROSS_COMPILE= on the make command line.
Rob
From swarren@wwwdotorg.org Wed Aug 21 20:24:41 2013
Received: with ECARTIS (v1.0.0; list linux-mips); Wed, 21 Aug 2013 20:24:43 +0200 (CEST)
Received: from avon.wwwdotorg.org ([70.85.31.133]:38199 "EHLO
avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org
with ESMTP id S6839074Ab3HUSYlLM8yj (ORCPT
<rfc822;linux-mips@linux-mips.org>); Wed, 21 Aug 2013 20:24:41 +0200
Received: from severn.wwwdotorg.org (unknown [192.168.65.5])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by avon.wwwdotorg.org (Postfix) with ESMTPS id 06F106351;
Wed, 21 Aug 2013 12:24:39 -0600 (MDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by severn.wwwdotorg.org (Postfix) with ESMTPSA id E26BAE461B;
Wed, 21 Aug 2013 12:24:35 -0600 (MDT)
Message-ID: <521505E2.3050308@wwwdotorg.org>
Date: Wed, 21 Aug 2013 12:24:34 -0600
From: Stephen Warren <swarren@wwwdotorg.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: James Hogan <james.hogan@imgtec.com>
CC: Ralf Baechle <ralf@linux-mips.org>,
Stephen Warren <swarren@nvidia.com>,
Michal Marek <mmarek@suse.cz>,
Shawn Guo <shawn.guo@linaro.org>,
Ian Campbell <ian.campbell@citrix.com>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
Rob Herring <rob.herring@calxeda.com>,
linux-mips@linux-mips.org, devicetree@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] MIPS: add <dt-bindings/> symlink
References: <1377095762-18926-1-git-send-email-james.hogan@imgtec.com>
In-Reply-To: <1377095762-18926-1-git-send-email-james.hogan@imgtec.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.97.8 at avon.wwwdotorg.org
X-Virus-Status: Clean
Return-Path: <swarren@wwwdotorg.org>
X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0)
X-Orcpt: rfc822;linux-mips@linux-mips.org
Original-Recipient: rfc822;linux-mips@linux-mips.org
X-archive-position: 37634
X-ecartis-version: Ecartis v1.0.0
Sender: linux-mips-bounce@linux-mips.org
Errors-to: linux-mips-bounce@linux-mips.org
X-original-sender: swarren@wwwdotorg.org
Precedence: bulk
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
List-software: Ecartis version 1.0.0
List-Id: linux-mips <linux-mips.eddie.linux-mips.org>
X-List-ID: linux-mips <linux-mips.eddie.linux-mips.org>
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
X-list: linux-mips
Content-Length: 699
Lines: 14
On 08/21/2013 08:36 AM, James Hogan wrote:
> Add symlink to include/dt-bindings from arch/mips/boot/dts/include/ to
> match the ones in ARM and Meta architectures so that preprocessed device
> tree files can include various useful constant definitions.
>
> See commit c58299a (kbuild: create an "include chroot" for DT bindings)
> merged in v3.10-rc1 for details.
>
> MIPS structures it's dts files a little differently to other
> architectures, having a separate dts directory for each SoC/platform,
> but most of the definitions in the dt-bindings/ directory are common so
> for now lets just have a single "include chroot" for all MIPS platforms.
Acked-by: Stephen Warren <swarren@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Richard Weinberger <richard@nod.at>,
Linux-Arch <linux-arch@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>, Ralf Baechle <ralf@linux-mips.org>,
Paul Mundt <lethal@linux-sh.org>, Jeff Dike <jdike@addtoit.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [RFC] Get rid of SUBARCH
Date: Wed, 21 Aug 2013 12:25:11 -0500 [thread overview]
Message-ID: <1377105911.2737.94@driftwood> (raw)
Message-ID: <20130821172511.HZNYaIaynJGc-Pjd5QUPsUk7sq0G0dPrE_31gVcHWsw@z> (raw)
In-Reply-To: <CAMuHMdWk-EPTNmPB1O1+F7YVQLjhQsFJznYwA3t6UCGUU1T9PQ@mail.gmail.com> (from geert@linux-m68k.org on Wed Aug 21 07:07:33 2013)
On 08/21/2013 07:07:33 AM, Geert Uytterhoeven wrote:
> On Wed, Aug 21, 2013 at 10:19 AM, Richard Weinberger <richard@nod.at>
> wrote:
> > This series is an attempt to remove the SUBARCH make parameter.
> > It as introduced at the times of Linux 2.5 for UML to tell the UML
> > build system what the real architecture is.
> >
> > But we actually don't need SUBARCH, we can store this information
> > in the .config file.
>
> Haha, now you have OS_ARCH (shouldn't that be called HOST_ARCH?)
> instead,
> which is available only for UM?
>
> > The series touches also m68k, sh, mips and unicore32.
> > These architectures magically select a cross compiler if ARCH !=
> SUBARCH.
> > Do really need that behavior?
>
> This does remove functionality.
> It allows to build a kernel using e.g. "make ARCH=m68k".
make ARCH=m68k CROSS_COMPILE=m68k-
make ARCH=arm CROSS_COMPILE=armv5l-
make ARCH=sparc CROSS_COMPILE=sparc-
make ARCH=ppc CROSS_COMPILE=powerpc-
make ARCH=sh CROSS_COMPILE=sh4-
make ARCH=mips CROSS_COMPILE=mipsel-
make ARCH=x86 CROSS_COMPILE=i686-
make ARCH=alpha CROSS_COMPILE=alpha-
Works the same way on all the targets I've tried so far. You specify
the architecture, you specify the cross compiler prefix, you feed it a
config file, you build.
(If a target supplies its own default cross compiler prefix I just have
to override it with what mine's called anyway...)
> Perhaps this can be moved to generic code? Most (not all!)
> cross-toolchains
> are called $ARCH-{unknown-,}linux{,-gnu}.
> Exceptions are e.g. am33_2.0-linux and bfin-uclinux.
The linaro toolchain is arm-linux-gnueabihf- and the one on kernel.org
is arm-unknown-linux-gnueabi- and the one I build is armv5l- (because
the FSF's
$ARCH-unknown-gnu-format-tuple-all-hail-stallman-gnu-gnu-gnu-dammit-gcc
is just nuts: why would I say -linux- in a linux-to-linux toolchain? Do
windows toolchains say -windows-?)
Other toolchain sources use other prefixes (-unknown- is often
-$VENDORNAME-), and then of course there's llvm... which is why you
specify CROSS_COMPILE= on the make command line.
Rob
next prev parent reply other threads:[~2013-08-21 17:25 UTC|newest]
Thread overview: 44+ 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
[not found] ` <52454E58.3010305@gmx.de>
2013-09-27 9:26 ` Richard Weinberger
2013-08-21 8:19 ` [PATCH 2/8] um: Do not use SUBARCH Richard Weinberger
2013-08-21 8:19 ` 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
[not found] ` <CALkWK0=FG4COEjv5+mu1JRiiFQ2k6vop1mhFPmAT4bjtYeK6nA@mail.gmail.com>
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 [this message]
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:41 ` Rob Landley
2013-08-22 20:55 ` David Daney
2013-08-22 21:32 ` Rob Landley
2013-08-22 21:32 ` Rob Landley
2013-08-21 12:53 ` Thorsten Glaser
2013-08-21 12:58 ` H. Peter Anvin
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=1377105911.2737.94@driftwood \
--to=rob@landley.net \
--cc=geert@linux-m68k.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=hpa@zytor.com \
--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@lists.linux-m68k.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=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