Subject: Re: Is the 2.6 dependency information complete? Doesn't look so...
From: Dave Dillow <dave@thedillows.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
In-Reply-To: <20040301060859.GA2129@mars.ravnborg.org>
References: <20040229235150.GA6327@merlin.emma.line.org>
	 <20040301060859.GA2129@mars.ravnborg.org>
Content-Type: text/plain
Message-Id: <1078163528.22900.17.camel@dillow.idleaire.com>
Mime-Version: 1.0
Date: Mon, 01 Mar 2004 12:52:08 -0500
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1346
Lines: 31

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>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/