From: Sam Ravnborg <sam@ravnborg.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-rc1-git1 -- Build error "make: *** [include/linux/version.h] Error 2"
Date: Thu, 19 Jan 2006 10:23:20 +0100 [thread overview]
Message-ID: <20060119092320.GA8588@mars.ravnborg.org> (raw)
In-Reply-To: <a44ae5cd0601190115y6f6e93a1y6b6b6284280259fd@mail.gmail.com>
On Thu, Jan 19, 2006 at 01:15:49AM -0800, Miles Lane wrote:
> I do have .kernelrelease that contains:
> "2.6.16-rc1-mm1 .file null .ident
> GCC:(GNU)4.0.320060115(prerelease)(Ubuntu4.0.2-7ubuntu1) .section
> .note.GNU-stack,,@progbits"
> I tried deleting it, but it gets recreated.
>
> I'm pretty frustrated. I have built hundreds of kernels and have not
> hit this problem before.
>
> Any help is most appreciated!
This can also be a side-effect of /dev/null being damaged.
In scripts/kconfig/lxdialog/check-lxdialog.sh we do:
echo main() {} | gcc -nncursesw -cx - -o /dev/null
I could imagine that your /dev/null has become a regular file and is now
filled with garbage.
And then the trick:
cat /dev/null $(wildcard .kernelrelease)
causes KERNELRELEASE to be full of crap.
Care to check that?
I have not a patch ready to fix the /dev/null issue - later today.
Sam
next prev parent reply other threads:[~2006-01-19 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 6:47 Miles Lane
2006-01-19 7:35 ` Sam Ravnborg
2006-01-19 9:15 ` Miles Lane
2006-01-19 9:23 ` Sam Ravnborg [this message]
2006-01-20 6:43 ` Nigel Cunningham
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
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=20060119092320.GA8588@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
/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
Powered by JetHome