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]

Date:	Thu, 27 May 2010 17:03:29 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Cc:	Américo Wang <xiyou.wangcong@...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, May 27, 2010 at 10:53:41AM +0530, Jaswinder Singh Rajput wrote:
>On Thu, May 27, 2010 at 10:01 AM, Américo Wang <xiyou.wangcong@...il.com> wrote:
>> On Thu, May 27, 2010 at 09:39:51AM +0530, Jaswinder Singh Rajput wrote:
>>>
>>>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'.
>>
>
>Ahh, then kbuild is buggy, kbuild should check .config instead of
>'uname -m' and verify from user if it mismatches.
>

Why? You didn't use 'make oldconfig', why shoud it check?
--
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/