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 23:43:54 +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

On Fri, 2015-04-03 at 19:23 +0200, Borislav Petkov wrote:
> On Fri, Apr 03, 2015 at 05:33:03PM +0200, Paul Bolle wrote:
> > Well, "when building on 32 bits" it currently suffices to do:
> >     make allnoconfig
> > 
> > and the patch changes that.
> 
> Hmm, so this would need more staring. The fact that 64-bit needs to set
> CONFIG_64BIT, we would need a way to say:
> 
> 	option allnoconfig_y if ARCH = "x86"
> 
> And Kconfig doesn't support that yet...

The fact that "make allnoconfig" and "make allyesconfig" can give you
a .config for another subarchitecture is annoying. I think it would be
nice if we teach those make targets (through tweaks in Kconfig files
and/or Makefiles) to avoid doing that.

Not sure, yet, how a clean way to do that might look like, sorry.


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/