From: "Giacomo A. Catenazzi" <cate@debian.org>
To: Bram Adams <Bram.Adams@ugent.be>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: The evolution of the Linux kernel build system
Date: Thu, 20 Mar 2008 16:22:03 +0100 [thread overview]
Message-ID: <47E2811B.9000100@debian.org> (raw)
In-Reply-To: <9048849A-9578-40E7-BD0E-FF2CD34F9372@ugent.be>
Bram Adams wrote:
> We would like to thank Sam Ravnborg and Kai Germaschewski for their
> constructive comments on an earlier version of the report. Any feedback
> on the published report or suggestions for further analysis are gladly
> appreciated.
Now I've done only a quick look.
I think you missed a point about dependencies.
Also in the old method, the .h dependencies were calculated
on build time (with the gcc -MM option IIRC).
But big problem is the dependencies of configuration.
Instead of having the dependency of config.h,
the kbuild checks about changes on every single
configuration item.
So "make dep" read the sources looking for CONFIG_ options.
IIRC it was a separate step, not to check file
for CONFIG_ string at every modification.
"make dep" was not so mandatory after every patch,
and anyway before big releases a "make mrproper"
was still recommended.
There was a lot of active development on this program,
to increment speed, and AFAIK no other project split
header dependencies in a more precise way.
This weekend I'll read carefully the paper and I'll give
you more comments.
ciao
cate
prev parent reply other threads:[~2008-03-20 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 14:19 The evolution of the Linux kernel build system Bram Adams
2008-03-20 15:01 ` Randy Dunlap
2008-03-26 22:37 ` Bram Adams
2008-03-20 15:22 ` Giacomo A. Catenazzi [this message]
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=47E2811B.9000100@debian.org \
--to=cate@debian.org \
--cc=Bram.Adams@ugent.be \
--cc=linux-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.