| 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
| ||
|
Message-ID: <1306845158.2029.543.camel@i7.infradead.org> Date: Tue, 31 May 2011 13:32:37 +0100 From: David Woodhouse <dwmw2@...radead.org> To: Ted Ts'o <tytso@....edu> Cc: Ingo Molnar <mingo@...e.hu>, x86@...nel.org, linux-kernel@...r.kernel.org, Alexey Dobriyan <adobriyan@...il.com>, Randy Dunlap <rdunlap@...otime.net> Subject: Re: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig' On Tue, 2011-05-31 at 08:12 -0400, Ted Ts'o wrote: > I don't know why Ingo needs ARCH=x86 on the command line, but I > regularly type "make ARCH=i386" when building 32-bit kernels on a > 64-bit system, and my scripts use "make ARCH=x86_64" when building > 64-bit kernels (just in case I happen to have booted a 32-bit > kernel). Yes. That's because of the problem described in $SUBJECT. Historically, the setting of CONFIG_64BIT in your .config file was just completely ignored in most cases. If you specified ARCH=i386 or ARCH=x86_64 on the command line it would be set accordingly, but if you *didn't* set it explicitly then the build system would *still* ignore what's in the existing .config, and just override it to match the host! The *only* time that the .config would be honoured was if you explicitly added ARCH=x86 to the command line. That's why your scripts grew these hacks, presumably. -- dwmw2 -- 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