[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100526223101.3f2dd7dd.rdunlap@xenotime.net>
Date: Wed, 26 May 2010 22:31:01 -0700
From: Randy Dunlap <rdunlap@...otime.net>
To: Américo Wang <xiyou.wangcong@...il.com>
Cc: Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Sam Ravnborg <sam@...nborg.org>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: config automatically switches from 32-bit to 64-bit for x86
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@...k.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 ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists