From: Randy Dunlap <rdunlap@xenotime.net>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
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: Wed, 26 May 2010 22:31:01 -0700 [thread overview]
Message-ID: <20100526223101.3f2dd7dd.rdunlap@xenotime.net> (raw)
In-Reply-To: <20100527043123.GA5349@cr0.nay.redhat.com>
On Thu, 27 May 2010 12:31:23 +0800 Américo Wang wrote:
> On Thu, May 27, 2010 at 09:39:51AM +0530, Jaswinder Singh Rajput wrote:
> >Hello Rafael,
> >
> >On Thu, May 27, 2010 at 5:43 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> 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'.
> >>
> >
> >Yes, this works :-)
>
>
> I think 'make ARCH=i386 menuconfig' also works.
Yes, that's what I use. I wasn't familiar with the "linux32 make ..." usage.
> >But I wonder then what is the point/use of CONFIG_X86_32 if compiler
> >is not listening to it.
> >
> >Logically compiler should set appropriate flags based on .config settings.
> >
>
> It's not compiler, it's kbuild, kbuild tries to determine the arch
> by 'uname -m'.
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-27 5:31 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 [this message]
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=20100526223101.3f2dd7dd.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--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®