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: <20100527154916.GA5585@infradead.org>
Date:	Thu, 27 May 2010 11:49:16 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Cc:	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 05:37:36AM +0530, 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.
> 
> Is this a BUG or did intentionally.

I think it's intentional, but I'm really annoyed by this behaviour.
I really don't want my config to change from a normal make depending
on uname output.  We do have a CONFIG_64BIT in .config which should
be respected.  uname output is a good indicator for a previously
unconfigured kernel, but shouldn't change settings for a fully
congigured build.  Forgetting the linux32 command happens at least two
dozen times to me everyday, leading to a few lost seconds that add
up in the end.

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