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:	Mon, 05 Nov 2007 16:47:36 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Guillaume Chazarain <guichaz@...oo.fr>
CC:	Sam Ravnborg <sam@...nborg.org>, Roland Dreier <rdreier@...co.com>,
	Christoph Hellwig <hch@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86"

Guillaume Chazarain wrote:
> On 11/6/07, H. Peter Anvin <hpa@...or.com> wrote:
>> The issue with "make allyesconfig" concerns me, although the same
>> situation already exists with any multiple-choice configuration.  What I
>> guess we really want is to be able to specify a few specific choices.
> 
> I don't know enough about Kbuild to know if it's possible or not, but I
> would find it great if the *config targets could take CONFIG_ variables
> on the command line, like:
> 
> make oldconfig CONFIG_SMP=y
> 
> If it's not possible, why not inherit the CONFIG_ options from environment
> variables, like we already do for $CFLAGS, but only at make *config
> time in this case?
> 

It probably can only be done at *config time (and probably *should* only 
be done at *config time); but it seems like it would be a 
straightforward addition to Kconfig to look in the environment for 
variables named CONFIG_* just like it'd look in an old config file.

That would definitely resolve a lot of issues.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ