From: Matthew Wilcox <willy@debian.org>
To: Chuck Slivkoff <charles_slivkoff@hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.4.16-pa16 (from CVS) fails on "make depend"
Date: Mon, 10 Dec 2001 22:42:15 +0000 [thread overview]
Message-ID: <20011210224215.L3427@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3C1539B8.A3175E86@hp.com>; from charles_slivkoff@hp.com on Mon, Dec 10, 2001 at 05:39:52PM -0500
On Mon, Dec 10, 2001 at 05:39:52PM -0500, Chuck Slivkoff wrote:
> I did a CVS update yesterday and tried to build a kernel today, using
> the same .config from my last successful build (2.4.9-pa78).
>
> After a "make clean", "make depend" is failing with the error below.
> I've done a "make menuconfig" and things seem to be OK.
>
> Anyone have any suggestions?
are you using the `approved' .cvsrc in build-tools? seems you're missing
-P to your update command.
--
Revolutions do not require corporate support.
prev parent reply other threads:[~2001-12-10 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 22:39 [parisc-linux] 2.4.16-pa16 (from CVS) fails on "make depend" Chuck Slivkoff
2001-12-10 22:41 ` Peter Mottram
2001-12-10 22:42 ` Matthew Wilcox [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=20011210224215.L3427@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=charles_slivkoff@hp.com \
--cc=parisc-linux@lists.parisc-linux.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