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 18:35:12 +0200
From:	Matthias Schniedermeyer <ms@...d.de>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
	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 27.05.2010 12:13, Christoph Hellwig wrote:
> On Thu, May 27, 2010 at 06:11:34PM +0200, Matthias Schniedermeyer wrote:
> > Just use ARCH=x86. That ARCH respects CONFIG_64BIT from .config and 
> > "CONFIG_64BIT" is a config-option (the very first in menuconfig)
> 
> Which is an obsolute pain to type, even worse than doing a linux32 call
> first.  Really, a simple
> 
> 	make
> 
> should default to do the right thing.

In my case it's wonderful, i compile several kernels with different 
bitnesses for differnt machines and with ARCH=x86 i don't have to 
differentiate between an i386 or x86_64 target.

for dat in a b c d; do make ARCH=x86 O=../$dat ; done





Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.

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