From: "David Luyer" <david@luyer.net>
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 22:05:54 +1100 [thread overview]
Message-ID: <200601191105.k0JB5sKN012313@typhaon.pacific.net.au> (raw)
In-Reply-To: <a44ae5cd0601182247h1b173289ncbc6dc405cbb0bb4@mail.gmail.com>
On Wed, Jan 18, 2006 at 10:47:13PM -0800, Miles Lane wrote:
> make all install modules modules_install
> /bin/sh: -c: line 0: syntax error near unexpected token `('
> /bin/sh: -c: line 0: `set -e; echo ' CHK
> include/linux/version.h'; mkdir -p include/linux/; if [ `echo -n
> "2.6.16-rc1-git1 .file null .ident
> GCC:(GNU)4.0.320060115(prerelease)(Ubuntu4.0.2-7ubuntu1) .section
> .note.GNU-stack,,@progbits" | wc -c ` -gt 64 ]; then echo
> '"2.6.16-rc1-git1 .file null .ident
[...]
Happens for me also (on latest snapshot).
/dev/null is removed by this line in check-lxdialog.sh during a
'make menuconfig':
echo "main() {}" | $cc -lncursesw -xc - -o /dev/null 2> /dev/null
This only happens if you don't have a libncursesw installed (not sure
if it is compiler dependant as well).
/dev/null being removed has many side-effects, this is just one of them.
Obviously 'cd /dev; ./MAKEDEV null' will fix. Oh, and fixing the script
would be useful too ;-)
David.
--
Pacific Internet (Australia) Pty Ltd
Business card: http://www.luyer.net/bc.html
Important notice: http://www.pacific.net.au/disclaimer/
next prev parent reply other threads:[~2006-01-19 11:06 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
2006-01-20 6:43 ` Nigel Cunningham
2006-01-19 11:05 ` David Luyer [this message]
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=200601191105.k0JB5sKN012313@typhaon.pacific.net.au \
--to=david@luyer.net \
--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
all inboxes | Powered by JetHome®