From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Is the 2.6 dependency information complete? Doesn't look so...
Date: Mon, 01 Mar 2004 00:59:30 +0100 [thread overview]
Message-ID: <yw1xeksd1lp9.fsf@kth.se> (raw)
In-Reply-To: <20040229235150.GA6327@merlin.emma.line.org>
Matthias Andree <matthias.andree@gmx.de> writes:
> Hi,
>
> I've just seen, after a BK pull:
>
> CC fs/nfsd/nfsctl.o
> fs/nfsd/nfsctl.c:28:30: linux/nfsd_idmap.h: no such file or directory
>
> This is a hint the dependency information isn't complete, otherwise, GNU
> make would've "get"^Wgot the include file.
That's right. Running bk -r get before building is advisable.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-02-29 23:59 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 [this message]
2004-03-01 6:08 ` Sam Ravnborg
2004-03-01 17:52 ` Dave Dillow
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=yw1xeksd1lp9.fsf@kth.se \
--to=mru@kth.se \
--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®