From: David Woodhouse <dwmw2@infradead.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: honor the ARCH setting of the existing configuration
Date: Sun, 31 Jul 2011 23:34:45 +0100 [thread overview]
Message-ID: <1312151687.18010.31.camel@i7.infradead.org> (raw)
In-Reply-To: <CACqU3MXak0Yo+VDQNEqT9rTJ5CjdU6jJ-C1Km7GauMQ+qGW+vg@mail.gmail.com>
On Sun, 2011-07-31 at 18:07 -0400, Arnaud Lacombe wrote:
> I think you totally miss the point of the patch as you keep being
> self-centered on x86.
I'm focusing on x86 at the moment because x86 is the only architecture
that's *broken* in this respect. The other architectures that you
mention below, where they support 64-bit kernels, all work fine with
only *one* ARCH= setting covering all configurations. It's only x86
where we haven't actually *finished* the merge.
> I am working with configuration for mips, sh, powerpc, arm and x86.
> Some of them are for real board, some of them are to regress-test
> compilers, binutils and kernel builds. Each of those config hardcode
> the CROSS_COMPILER string and have their own build directory. In each
> case, I want to be able to just run "make O=/src/obj/v3.0-arm
> oldnoconfig all" without having to worry about anything else.
Yes, that's a valid but *separate* problem. FWIW I usually solve this
problem with a two-line GNUmakefile:
ARCH := arm
include Makefile
I haven't checked whether it works for out-of-source-tree builds; I bet
it could be made to.
I would love to see $ARCH turned into a proper configuration option.
--
dwmw2
next prev parent reply other threads:[~2011-07-31 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 19:44 [PATCH] kbuild: honor the ARCH setting of the existing configuration Aunt Tillie
2011-07-31 20:20 ` David Woodhouse
2011-07-31 22:07 ` Arnaud Lacombe
2011-07-31 22:34 ` David Woodhouse [this message]
2011-07-31 23:20 ` Arnaud Lacombe
2011-08-01 2:05 ` Randy Dunlap
2011-08-01 8:42 ` David Woodhouse
2011-08-01 17:33 ` Arnaud Lacombe
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=1312151687.18010.31.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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