From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.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: Thu, 27 May 2010 02:13:42 +0200 [thread overview]
Message-ID: <201005270213.42913.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTik0PUKP3QLPRbb3nlh034_inmaeVbXy3q5_LQz-@mail.gmail.com>
On Thursday 27 May 2010, 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.
Try 'linux32 make menuconfig' and 'linux32 make'.
Rafael
next prev parent reply other threads:[~2010-05-27 0:12 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 [this message]
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
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=201005270213.42913.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.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