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, 4 Feb 2011 14:35:29 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Ulf Magnusson <ulfalizer.lkml@...il.com>
Cc:	linux-kbuild@...r.kernel.org, zippel@...ux-m68k.org,
	mmarek@...e.cz, akpm@...ux-foundation.org,
	andrea.gelmini@...ma.net, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH] [ANNOUNCE] kconfig: Kconfiglib: a flexible Python
 Kconfig parser

On Wed, 2 Feb 2011 00:27:55 +0100 Ulf Magnusson wrote:

> Hi,
> 
> This is the initial release of Kconfiglib: a Python library for
> scripting, debugging, and extracting information from Kconfig-based
> configuration systems.  It can be used to programmatically generate a
> .config when the '*conf' tools are too inflexible, to quickly find out
> interesting information about a Kconfig configuration such as dependency
> relations between symbols and where undefined symbols are referenced,
> and in applications that need to parse and extract information from
> Kconfig files.
> 
> For a much longer introduction including multiple examples, see
> arch/kconfig/kconfiglib.py.
> 
> Have fun!
> 
> Signed-off-by: Ulf Magnusson <ulfalizer.lkml@...il.com>
> ---
> Convenience links:
> 
> Documentation, generated from kconfiglib.py with pydoc -w:
> http://dl.dropbox.com/u/10406197/kconfiglib.html
> 
> Examples as separate files:
> http://dl.dropbox.com/u/10406197/kconfiglib-examples.tar.gz
> 
> 
> The patch should be preferably be applied to a recent kernel, i.e. Linus's
> (2.6.38-rc3 at the time of writing).  Due to recent Kconfig changes, the
> kconfigtest.py test suite - which compares output character-for-character -
> will indicate failure on older (a few months old) kernels versions even though
> the outputs are functionally equivalent.
> 
>  Documentation/kbuild/kconfig-language.txt |    5 +
>  Documentation/kbuild/kconfig.txt          |    8 +
>  README                                    |   13 +
>  scripts/kconfig/Makefile                  |   26 +-
>  scripts/kconfig/kconfiglib.py             | 3918 +++++++++++++++++++++++++++++
>  scripts/kconfig/kconfigtest.py            |  396 +++
>  6 files changed, 4365 insertions(+), 1 deletions(-)
>  create mode 100644 scripts/kconfig/kconfiglib.py
>  create mode 100644 scripts/kconfig/kconfigtest.py
> 

> diff --git a/README b/README
> index 1b81d28..bb5e68f 100644
> --- a/README
> +++ b/README
> @@ -196,6 +196,19 @@ CONFIGURING the kernel:
>  			   values to 'n' as much as possible.
>  	"make randconfig"  Create a ./.config file by setting symbol
>  			   values to random values.
> +	"make scriptconfig SCRIPT=<path to script>" Run a Kconfiglib
> +			   script (see scripts/kconfig/kconfiglib.py).  This
> +			   can be used to programatically generate a
> +			   ./.config, and for applications that need to
> +			   extract information from Kconfig files.
> +	"make iscriptconfig" Launch an interactive Python shell
> +			   for running Kconfiglib on the architecture's
> +			   Kconfig configuration.  The kconfiglib and sys
> +			   (for sys.argv[1] - the base Kconfig file) modules
> +			   will be imported automatically, and a Config
> +			   instance 'c' will be created for the architecture
> +			   (using c = kconfiglib.Config(sys.argv[1])).
> +
>  
>     You can find more information on using the Linux kernel config tools
>     in Documentation/kbuild/kconfig.txt.

Hi Ulf,

This is interesting.  I just wish I could read it.  ;)
I'll get over it.


1.  It would be really Good to have "make scriptconfig SCRIPT=<path to script>"
and "make iscriptconfig" (similar to above, but shortened) in "make help" output.

2.  My first test (using your ex1.py script) failed because I used O=xx64 (build
directory):

rddunlap@...mera:lnx-2638-rc3> make O=xx64 scriptconfig SCRIPT=~/pkg/kconfiglib/ex1.py
  GEN     /lnx/src/lnx-2638-rc3/xx64/Makefile
Traceback (most recent call last):
  File "/home/rddunlap/pkg/kconfiglib/ex1.py", line 1, in <module>
    import kconfiglib
ImportError: No module named kconfiglib
make[2]: *** [scriptconfig] Error 1
make[1]: *** [scriptconfig] Error 2
make: *** [sub-make] Error 2

Does kconfiglib support O=builddir generally?  I can't tell that it does (yet)
since all ex[1-7].py fail in this manner.
It needs to support/allow O=builddir.

Thanks.  I'll keep looking...

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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