From: Roman Zippel <zippel@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: linux kernel conf 0.7
Date: Sat, 28 Sep 2002 16:25:43 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0209281529580.338-100000@serv> (raw)
Hi,
At http://www.xs4all.nl/~zippel/lc/ you can find the latest version of the
new config system. Besides the usual archive there is also now a patch
against a 2.5.39 kernel and finally some documentation. This patch I also
consider as my first release canditate, so please test this one carefully,
this release contains pretty much everything I want from the first release
to be integrated into the kernel.
Other changes:
- update to 2.5.39
- seperate kernel Makefile (by Sam Ravnborg/Kai Germaschewski)
- lots of qconf fine tuning
- the generated config files are now named Build.conf and use tabs
instead of two spaces, which makes it easier to read.
An issue (which was also mentioned by Jeff Garzik) is the help text
format. Jeff likes to have an endhelp, where I think it's redundant. The
parser currently checks the amount of indendation to find the end of the
help text, this makes the help text quite easy to read and parse. If
someone prefers an endhelp (or has an even better idea), please speak up
now, if enough people complain, I have no problem changing it.
If someone is still wondering, why he should use lkc, as he is happy with
"make oldconfig", look at this comparison. Current version:
$ time make oldconfig
/bin/sh ./scripts/Configure -d arch/i386/config.in
#
# Using defaults found in .config
#
...
real 0m13.213s
user 0m5.520s
sys 0m5.440s
New version:
$ time make oldconfig
make[1]: Entering directory `/home/roman/src/lc'
make[1]: `conf' is up to date.
make[1]: Leaving directory `/home/roman/src/lc'
./scripts/lkc/conf -o arch/i386/Build.conf
#
# using defaults found in .config
#
...
real 0m0.473s
user 0m0.220s
sys 0m0.050s
These are the numbers from cache, so you have to add the amount of time
needed to read the config files from disk. The new files are larger as
they include the help text, but as long as you don't configure over a very
slow network, it will still be faster.
bye, Roman
next reply other threads:[~2002-09-28 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 14:25 Roman Zippel [this message]
2002-09-28 14:42 ` Tomas Szepe
2002-09-28 15:15 ` Roman Zippel
2002-09-28 15:41 ` Roman Zippel
2002-09-28 22:48 ` Sam Ravnborg
2002-09-29 0:00 ` Roman Zippel
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=Pine.LNX.4.44.0209281529580.338-100000@serv \
--to=zippel@linux-m68k.org \
--cc=kbuild-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®