From: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "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>,
"Américo Wang" <xiyou.wangcong@gmail.com>
Subject: Re: config automatically switches from 32-bit to 64-bit for x86
Date: Sat, 29 May 2010 22:49:25 +0530 [thread overview]
Message-ID: <AANLkTiku0kPykE30DIQvOD9gauEGZbyeDWXGkLb53sgJ@mail.gmail.com> (raw)
In-Reply-To: <20100529111951.GB31550@merkur.ravnborg.org>
Hello Sam and Américo,
On Sat, May 29, 2010 at 4:49 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Fri, May 28, 2010 at 03:37:00AM +0530, Jaswinder Singh Rajput wrote:
>> Hello Sam,
>>
>> On Fri, May 28, 2010 at 12:16 AM, Sam Ravnborg <sam@ravnborg.org> wrote:
>> > On Thu, May 27, 2010 at 11:49:16AM -0400, Christoph Hellwig wrote:
>> >> On Thu, May 27, 2010 at 05:37:36AM +0530, Jaswinder Singh Rajput wrote:
>> >> > Hello,
>> >> >
>> >> > I am trying to build 32 bit kernel image on 64-bit machine but after
>> >> > 'make menuconfig' it automatically switches 32-bit to 64-bit.
>> >> >
>> >> > Is this a BUG or did intentionally.
>> >>
>> >> I think it's intentional, but I'm really annoyed by this behaviour.
>> >
>> > The request when we did the merge of 32 and 64 bit was that we
>> > should continue to build 64bit kernels on 64 bit machines.
>> > And likewise for 32bit.
>> > Because this was what the users where used to.
>> >
>> > We could simplify metters by defining new rules.
>> > As you suggest that uname on an intel box always resulted in ARCH=x86.
>> > But then people would complain why a 32 bit kernel is default when
>> > the box is 64 bit.
>> >
>> > Something like this:
>> > [The escape chars align nicely in the patched Makefile]
>> >
>> > Sam
>> >
>> > diff --git a/Makefile b/Makefile
>> > index ebc8225..e7f97a5 100644
>> > --- a/Makefile
>> > +++ b/Makefile
>> > @@ -161,10 +161,11 @@ export srctree objtree VPATH
>> > # then ARCH is assigned, getting whatever value it gets normally, and
>> > # SUBARCH is subsequently ignored.
>> >
>> > -SUBARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ \
>> > - -e s/arm.*/arm/ -e s/sa110/arm/ \
>> > +SUBARCH := $(shell uname -m | sed -e s/i.86/x86/ -e s/x86_64/x86/ \
>> > + -e s/sun4u/sparc64/ \
>> > + -e s/arm.*/arm/ -e s/sa110/arm/ \
>> > -e s/s390x/s390/ -e s/parisc64/parisc/ \
>> > - -e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
>> > + -e s/ppc.*/powerpc/ -e s/mips.*/mips/ \
>> > -e s/sh[234].*/sh/ )
>> >
>> > # Cross compiling and selecting different set of gcc/bin-utils
>> >
>> >
>>
>> Thanks, this patch fixes the issue. Now 'make menuconfig' is following .config.
>
> If you think this is the right way to do things you can take it up
> with the x86 maintainers.
>
> Although the patch touches only a generic file this is x86 specific.
>
Américo Wang, Do you mind handle this kconfig patch.
Thanks,
--
Jaswinder Singh.
next prev parent reply other threads:[~2010-05-29 17:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 0:07 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 [this message]
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
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=AANLkTiku0kPykE30DIQvOD9gauEGZbyeDWXGkLb53sgJ@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=x86@kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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®