[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1312151687.18010.31.camel@i7.infradead.org>
Date: Sun, 31 Jul 2011 23:34:45 +0100
From: David Woodhouse <dwmw2@...radead.org>
To: Arnaud Lacombe <lacombar@...il.com>
Cc: Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] kbuild: honor the ARCH setting of the existing
configuration
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
--
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