From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Paul P Komkoff Jr <i@stingr.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.19 - What's up with the kernel build?
Date: Thu, 30 May 2002 04:45:12 -0400 [thread overview]
Message-ID: <3CF5E698.2020806@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205292019090.9971-100000@chaos.physics.uiowa.edu>
Kai Germaschewski wrote:
>On Wed, 29 May 2002, Jeff Garzik wrote:
>
>
>
>>Well, I really like Keith's kbuild25 too, but Linus said (at least once)
>>he wanted an evolution to a new build system... not an unreasonable
>>request to at least consider. Despite Keith's quality of code (again --
>>I like kbuild25), his 3 patch submissions seemed a lot like ultimatums,
>>very "take it or leave it dammit". Not the best way to win friends and
>>influence people.
>>
>>If Keith is indeed leaving it, I'm hoping someone will maintain it, or
>>work with Kai to integrate it into 2.5.x.
>>
>>
>
>Oh well, it really wasn't my intention to start the good old kbuild-2.5
>thread at all.
>
>Anyway, I believe kbuild-2.5 has lots of useful ideas and I'll go pick
>pieces - from kbuild-2.5, from dancing-makefiles, from stuff I've done
>myself and work on improving the current build system. But I believe in
>make, and don't think I'll move away from it.
>
>One thing these patches show is that gradual improvement is actually
>possible, so far the kbuild process has gained quite some features with a
>lot of small patches - and some bigger ones, but these are only trivial
>cleanups.
>
>Of course it happened that I introduced some bugs in the process, but the
>fact that fixes were posted to linux-kernel by the next morning shows that
>it's obviously possible for other people to grasp what's going on and fix
>bugs. Rules.make is some 400 lines currently, that's quite a difference to
>kbuild-2.5 core's 30000 lines of code.
>
>Anyway, fortunately it's not up to me to decide what happens. From my
>perspective the plan is to go on with this gradual improvement, in
>particular
>o fix dependencies / modversions (that includes "make dep" going away)
>o allow for separate objdir (this one is actually easy for 95% of the
> compiled files which use standard rules, and lots of work for the
> remaining 5%. So it'll take time to remove the 5% special cases, after
> that things are pretty easy)
>
>
A small request to add to the list:
Current 2.4.x kernels build (at least on x86) with
-nostdinc -I /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.0.4/include
added to CFLAGS... IMOit is a good idea in general to build all kernel
code this way. (note that userland programs created during build should
not use this rule, of course)
next prev parent reply other threads:[~2002-05-30 8:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 20:22 2.5.19 - What's up with the kernel build? Kai Germaschewski
2002-05-29 20:50 ` Paul P Komkoff Jr
2002-05-29 20:58 ` Jeff Garzik
2002-05-29 22:38 ` Nicolas Pitre
2002-05-29 22:56 ` Thunder from the hill
2002-05-29 23:18 ` Nicolas Pitre
2002-05-29 23:29 ` Daniel Phillips
2002-05-29 23:06 ` Tomas Szepe
2002-05-29 23:40 ` Daniel Phillips
2002-05-30 0:17 ` Nicolas Pitre
2002-05-30 0:36 ` Daniel Phillips
2002-05-30 0:42 ` Jeff Garzik
2002-05-30 0:47 ` Robert Love
2002-06-03 6:49 ` Rusty Russell
2002-05-30 2:23 ` Nicolas Pitre
2002-05-30 2:30 ` Daniel Phillips
2002-05-30 2:00 ` Kai Germaschewski
2002-05-30 2:17 ` Daniel Phillips
2002-05-30 8:45 ` Jeff Garzik [this message]
2002-05-30 8:54 ` Erik Andersen
2002-05-30 9:01 ` Russell King
2002-05-30 9:32 ` Erik Andersen
2002-05-30 13:22 ` Kai Germaschewski
2002-05-29 22:14 ` Martin Dalecki
2002-05-29 23:22 ` Tom Rini
2002-05-29 22:45 ` Martin Dalecki
2002-05-30 0:33 ` Kai Germaschewski
2002-06-01 3:01 ` Kernel compile quiet mode Kevin O'Connor
2002-06-01 7:34 ` Kai Germaschewski
2002-06-01 15:08 ` Kevin O'Connor
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=3CF5E698.2020806@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=i@stingr.net \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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