Re: [kbuild-devel] Converting the 2.5 kernel to kbuild 2.5

[Christoph Hellwig <hch@caldera.de>]

On Tue, Dec 04, 2001 at 07:48:15AM -0500, Eric S. Raymond wrote:
> And, by the way, there is no CML1 :-).  Instead, there are four
> mutually incompatible dialects and a rulebase that breaks in different
> ways depending on which interpreter you use.  Well, maybe just three
> mutual incompatible dialects and one clone -- but it's notoriously
> hard to verify that two interpreters have the same accept language, so
> nobody knows for sure.

There is a CML1 language specification, as written down in a file, namely
Documentation/kbuild/config-language.txt in the kernel tree.
There is one tool (mconfig) which has a yacc-parser that implements that
specification completly, and some horrid ugly scripts in the tree that
parse them in a more or less working way.  There also are a number of
other tools I don't know to much about that understand the language as
well.

All of these tools just require the runtime contained in the LSB and no
funky additional script languages.  Also none needs a binary intermediate
representation of the config.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.