linux-kernel - Re: Additional kconfig targets (cloneconfig, nonint

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]

Message-ID: <alpine.LNX.1.10.0804301643140.5623@fbirervta.pbzchgretzou.qr>
Date:	Wed, 30 Apr 2008 16:44:30 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Sam Ravnborg <sam@...nborg.org>
cc:	linux-kbuild <linux-kbuild@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...emonkey.org.uk>,
	Roland McGrath <roland@...hat.com>,
	Andres Salomon <dilinger@...ued.net>
Subject: Re: Additional kconfig targets (cloneconfig, nonint_oldconfig etc)


On Tuesday 2008-04-29 20:35, Sam Ravnborg wrote:
>
>I plan to drop the 'very chatty' mode as I
>do not see it usefull.
>So in essense 'make oldconfig' and 'make silentoldconfig'
>become equal.

Sounds good.


>The commands we have today for kconfig is:
>
># Command line variants
>make oldconfig
>make silentoldconfig
>make defconfig
>make XXX_defconfig
>
>(The other frontends are left out on purpose).
>The challenge here is to come up with a syntax that
>allows us to select between the three behaviours,
>while keeping backward compatibility.
>
>The best suggestion I have so far is to say that:
>a) if defconfig is specified then we use method 1)
>b) if oldconfig is specified then we use method 2)
>c) if newconfig is specified then we use method 3)

[Where is 1) defined?]

>And we add support for a new 'commandline' parameter
>'K' so I can say:
>
>make K=/proc/config.gz defconfig
>make K=i386_defconfig  defconfig
>make K=i386_defconfig  oldconfig
>make K=/proc/config.gz newconfig
>
>So K is used to specify what config file we use
>to start out from.

Oh that's real good, even better than cloneconfig.

># Enviroment variables affecting kconfig
>KCONFIG_ALLCONFIG
>KCONFIG_NOSILENTUPDATE
>KCONFIG_CONFIG
>KCONFIG_OVERWRITECONFIG
>KCONFIG_NOTIMESTAMP
>KCONFIG_AUTOCONFIG
>KCONFIG_AUTOHEADER

Ok and these are doing .. what?

>#input files (aparts from the mandatory ones)
>all.config
>allno.config
>allmod.config
>allyes.config
>allrandom.config

Used for..?
--
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/