linux-kernel - Re: [PATCH] x86/Kconfig: Fix allnoconfig without explicitly specified ARCH

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:	Fri, 03 Apr 2015 17:33:03 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Ingo Molnar <mingo@...nel.org>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/Kconfig: Fix allnoconfig without explicitly
 specified ARCH

Borislav Petkov schreef op vr 03-04-2015 om 16:59 [+0200]:
> On Fri, Apr 03, 2015 at 03:42:18PM +0200, Paul Bolle wrote:
> > A side effect of this patch is that allnoconfig when building on 32 bits
> > now also requires to set ARCH=i386, which is surprising. This seems to
> 
> How else would you build a 32-bit allnoconfig?

Well, "when building on 32 bits" it currently suffices to do:
    make allnoconfig

and the patch changes that.

Just like it is surprising to get a CONFIG_X86_32=y .config when doing
allnoconfig on x86_64 it is also surprising to get a
CONFIG_X86_64=y .config when doing allyesconfig on i386. So I think a
more general solution to these surprising .configs should be considered.
 
Thanks,


Paul Bolle

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