From: Nigel Cunningham <ncunningham@cyclades.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Miles Lane <miles.lane@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-rc1-git1 -- Build error "make: *** [include/linux/version.h] Error 2"
Date: Fri, 20 Jan 2006 16:43:29 +1000 [thread overview]
Message-ID: <200601201643.29207.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060119092320.GA8588@mars.ravnborg.org>
Hi.
On Thursday 19 January 2006 19:23, Sam Ravnborg wrote:
> This can also be a side-effect of /dev/null being damaged.
I had precisely this problem last night. No idea what caused it, but that was
the issue. Wish I'd seen your email before I wasted time finding the
cause! :)
Nigel
next prev parent reply other threads:[~2006-01-20 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 6:47 2.6.16-rc1-git1 -- Build error "make: *** [include/linux/version.h] Error 2" Miles Lane
2006-01-19 7:35 ` Sam Ravnborg
2006-01-19 9:15 ` Miles Lane
2006-01-19 9:23 ` Sam Ravnborg
2006-01-20 6:43 ` Nigel Cunningham [this message]
2006-01-19 11:05 ` David Luyer
2006-01-19 19:59 ` Miles Lane
2006-01-19 20:05 ` Miles Lane
2006-01-19 20:07 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2006-01-19 8:41 joel.soete
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=200601201643.29207.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--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