From: Dave Dillow <dave@thedillows.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Is the 2.6 dependency information complete? Doesn't look so...
Date: Mon, 01 Mar 2004 12:52:08 -0500 [thread overview]
Message-ID: <1078163528.22900.17.camel@dillow.idleaire.com> (raw)
In-Reply-To: <20040301060859.GA2129@mars.ravnborg.org>
On Mon, 2004-03-01 at 01:08, Sam Ravnborg wrote:
> On Mon, Mar 01, 2004 at 12:51:50AM +0100, Matthias Andree wrote:
> > Will the kernel rebuild dependent files when includes change when this
> > information is missing? If so, how?
>
> kbuild scans for dependencies and build the output file in one go.
> Therefore from a make perspective it will not see the new dependency of
> nfsd_idmap.h when starting to compile nfsctl.c.
>
> Dependencies are first OK after first kernel compile.
> So if you tried twice the 'bk get' functionality should be OK.
Also, the changesets at bk://typhoon.bkbits.net/autoget-2.5 add
functionality to kbuild to checkout needed files automatically, as the
build progresses -- no more 'bk get' needed...
I haven't kept it up to date, but I doubt it'd need many changes to work
with a recent kernel. It's currently BK/SCCS specific, but I do not
think it would be hard to make it work with other version control
systems, as long as make supports them.
Since you do so much in kbuild, I'd love some comments on it, if you
have time.
--
Dave Dillow <dave@thedillows.org>
next prev parent reply other threads:[~2004-03-01 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 23:51 Matthias Andree
2004-02-29 23:59 ` Måns Rullgård
2004-03-01 6:08 ` Sam Ravnborg
2004-03-01 17:52 ` Dave Dillow [this message]
2004-03-02 18:07 ` Sam Ravnborg
2004-03-02 18:40 ` [PATCH 0/3] Auto checkout for kbuild Dave Dillow
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=1078163528.22900.17.camel@dillow.idleaire.com \
--to=dave@thedillows.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®