Re: [2.6 patch] x86: allow 64bit setting in Kconfig
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Fri, 1 Feb 2008 16:22:27 +0100
* Adrian Bunk <bunk@xxxxxxxxxx> wrote:
# Select 32 or 64 bit
config 64BIT
- bool "64-bit kernel" if ARCH = "x86"
+ bool "64-bit kernel"
default ARCH = "x86_64"
NACK. You have just broken:
make ARCH=i386 randconfig
on a 64-bit box that has a 32-bit .config in its kernel directory.
The randconfig/allyesconfig/allnoconfig variants override whatever is in
the current .config. Making the result depend on whatever is in the
.config at the moment is fundamentally wrong.
"oldconfig" on the other hand has correct sensitivity to the existing
.config - and that always worked correctly. So if you pop a 32-bit or a
64-bit .config into a kernel tree, that will be listened to, no matter
whether you are on a 32-bit or on a 64-bit host.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [2.6 patch] x86: allow 64bit setting in Kconfig
- From: Adrian Bunk
- Re: [2.6 patch] x86: allow 64bit setting in Kconfig
- Prev by Date: Re: Removing dev.power.power_state (WAS: Feature Removals for 2.6.25)
- Next by Date: Should nonblocking I/O calls to a disconnected device get an error? [was: Problem: hiddev stops sending events after some error recoveries]
- Previous by thread: Re: [PATCH] ipwireless: driver for 3G PC Card
- Next by thread: Re: [2.6 patch] x86: allow 64bit setting in Kconfig
- Index(es):
Relevant Pages
|
