linux-kernel - Re: config automatically switches from 32-bit to 64-bit for x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100527043123.GA5349@cr0.nay.redhat.com>
Date:	Thu, 27 May 2010 12:31:23 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Cc:	"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, 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.

>
>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'.
--
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/