From: Michal Marek <mmarek@suse.cz>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: config automatically switches from 32-bit to 64-bit for x86
Date: Fri, 04 Jun 2010 09:53:41 +0200 [thread overview]
Message-ID: <4C08B105.5050203@suse.cz> (raw)
In-Reply-To: <AANLkTik_QtJQKWYSYcFgjFvNjlqOWMV5iqBGeQeu4SuI@mail.gmail.com>
On 4.6.2010 08:23, Jaswinder Singh Rajput wrote:
> Hello Michal and Sam,
>
> On Thu, Jun 3, 2010 at 7:00 PM, Michal Marek <mmarek@suse.cz> wrote:
>> What about always making the prompt visible, so that the previously set
>> value gets reused? The downside is that 'make ARCH=i386 menuconfig' in a
>> clean tree on x86_64 will default to 64bit, because it will find the
>> setting in the config of the running 64bit kernel :(. But after manually
>> turning CONFIG_64BIT off, the setting will be preserved.
>>
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index dcb0593..05ec418 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -3,7 +3,7 @@ mainmenu "Linux Kernel Configuration for x86"
>>
>> # Select 32 or 64 bit
>> config 64BIT
>> - bool "64-bit kernel" if ARCH = "x86"
>> + bool "64-bit kernel"
>> default ARCH = "x86_64"
>> ---help---
>> Say yes to build a 64-bit kernel - formerly known as x86_64
>>
>
> This patch works !!
Does
$ make mrproper
$ make ARCH=i386 menuconfig
on x86_64 also work for you? Here, it takes CONFIG_64BIT=y from
/boot/config-`uname -r`. I see no easy way to solve this atm.
Michal
next prev parent reply other threads:[~2010-06-04 7:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 0:07 config automatically switches from 32-bit to 64-bit for x86 Jaswinder Singh Rajput
2010-05-27 0:13 ` Rafael J. Wysocki
2010-05-27 4:09 ` Jaswinder Singh Rajput
2010-05-27 4:31 ` Américo Wang
2010-05-27 5:23 ` Jaswinder Singh Rajput
2010-05-27 9:03 ` Américo Wang
2010-05-27 5:31 ` Randy Dunlap
2010-05-27 16:19 ` Geert Uytterhoeven
2010-05-27 20:21 ` Rafael J. Wysocki
2010-05-27 15:19 ` Matthias Schniedermeyer
2010-05-27 15:49 ` Christoph Hellwig
2010-05-27 16:11 ` Matthias Schniedermeyer
2010-05-27 16:13 ` Christoph Hellwig
2010-05-27 16:35 ` Matthias Schniedermeyer
2010-05-27 18:46 ` Sam Ravnborg
2010-05-27 22:07 ` Jaswinder Singh Rajput
2010-05-29 11:19 ` Sam Ravnborg
2010-05-29 17:19 ` Jaswinder Singh Rajput
2010-06-02 8:20 ` Américo Wang
2010-06-02 8:50 ` Sam Ravnborg
2010-06-03 13:30 ` Michal Marek
2010-06-04 6:23 ` Jaswinder Singh Rajput
2010-06-04 7:53 ` Michal Marek [this message]
2010-06-06 4:14 ` Jaswinder Singh Rajput
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=4C08B105.5050203@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--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