From: Christoph Hellwig <hch@caldera.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: build-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] mconfig 0.20 available
Date: Sat, 17 Nov 2001 18:32:20 +0100 [thread overview]
Message-ID: <20011117183220.A14033@caldera.de> (raw)
In-Reply-To: <20011116173840.A15515@caldera.de> <16782.1005994611@ocs3.intra.ocs.com.au>
In-Reply-To: <16782.1005994611@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Sat, Nov 17, 2001 at 09:56:51PM +1100
On Sat, Nov 17, 2001 at 09:56:51PM +1100, Keith Owens wrote:
> On Fri, 16 Nov 2001 17:38:40 +0100,
> Christoph Hellwig <hch@caldera.de> wrote:
> >The mconfig release 0.20 is now available.
> >
> >Mconfig is a tool to configure the linux kernel, similar to
> >make {menu,x,}config, but written in C and with a proper yacc
> >parser.
>
> Christoph, could you explain why this is being added now and how it
> compares to CML1 and/or CML2?
It's not added now - Michael started the development about 5 years ago,
in 1998 he stopped working on it. In 1999 or 2001 I started hacking on
it, only adding what I needed. Now I finally found the time to make a
formal release.
The tool mconfig parses CML1 rules, and does so _much_ more strictly
then any other parser.
> kbuild 2.[45] is completely agnostic about how .config and autoconf.h
> are built, the only requirement is that .config be internally
> consistent before it goes into the main build phase. I don't care how
> .config is built, but I do want to understand why another version of
> CML is being developed.
The current cml1 scripts are _very_ ugly, and even if cml2 makes it in
2.5 (yes, I don't like it - but I don't have to decide it..) kernels
using cml1 will be around for a long time.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-11-17 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 16:38 [ANNOUNCE] mconfig 0.20 available Christoph Hellwig
2001-11-17 10:56 ` Keith Owens
2001-11-17 17:32 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-18 11:38 Samium Gromoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011117183220.A14033@caldera.de \
--to=hch@caldera.de \
--cc=build-devel@lists.sourceforge.net \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox