From: Sam Ravnborg <sam@ravnborg.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: include localarch for simple cross overrides
Date: Wed, 29 Oct 2008 19:54:48 +0100 [thread overview]
Message-ID: <20081029185448.GB22105@uranus.ravnborg.org> (raw)
In-Reply-To: <1225304495-28079-1-git-send-email-vapier@gentoo.org>
On Wed, Oct 29, 2008 at 02:21:35PM -0400, Mike Frysinger wrote:
> For people banging on kernel trees which are dedicated to a specific arch,
> it'd be nice to allow the repo itself to declare the default ARCH (and
> CROSS_COMPILE) easily. Just like the "localversion-*" files, people can
> just do:
> echo 'ARCH ?= blackfin' > localarch
> and the tree will default to 'blackfin' all the time rather than whatever
> the build machine happens to be.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> Makefile | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index a7f2068..7fa1f81 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -180,6 +180,7 @@ SUBARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
> # make ARCH=ia64
> # Another way is to have ARCH set in the environment.
> # The default ARCH is the host where make is executed.
> +-include localarch
>
> # CROSS_COMPILE specify the prefix used for all executables used
> # during compilation. Only gcc and related bin-utils executables
Last time I did something similar it broke a few archs.
But then it was automatically done where this approach is mnually.
I will apply this to kbuild-next but it will most likely change
sometime in the future.
Sam
prev parent reply other threads:[~2008-10-29 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 18:21 Mike Frysinger
2008-10-29 18:54 ` Sam Ravnborg [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=20081029185448.GB22105@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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
all inboxes | Powered by JetHome®