From: "David Brown" <dmlb2000@gmail.com>
To: "Robin Cook" <rcook@wyrms.net>
Cc: Linux-kernel@vger.kernel.org
Subject: Re: compile failure on 2.6.19
Date: Sun, 31 Dec 2006 10:27:26 -0800 [thread overview]
Message-ID: <9c21eeae0612311027p17737cc0q765aca18fe22fd38@mail.gmail.com> (raw)
In-Reply-To: <1167585932.3730.9.camel@localhost>
On 12/31/06, Robin Cook <rcook@wyrms.net> wrote:
> I am getting this error when I try to compile 2.6.19 and 2.6.19.1.
>
> I ran make mrproper and make menuconfig then ran make and got the below
> error.
>
> HOSTLD scripts/kconfig/conf
> scripts/kconfig/conf -s arch/i386/Kconfig
> CHK include/linux/version.h
> UPD include/linux/version.h
> /bin/sh: -c: line 0: syntax error near unexpected token `('
> /bin/sh: -c: line 0: `set -e; echo ' CHK
> include/linux/utsrelease.h'; mkdir -p include/linux/; if [ `echo -n
> "2.6.19.1 .file null .ident
> GCC:(GNU)4.1.1 .section .note.GNU-stack,,@progbits" | wc -c ` -gt 64 ];
> then echo '"2.6.19.1 .file null .ident
> GCC:(GNU)4.1.1 .section .note.GNU-stack,,@progbits" exceeds 64
> characters' >&2; exit 1; fi; (echo \#define UTS_RELEASE \"2.6.19.1 .file
> null .ident GCC:(GNU)4.1.1 .section .note.GNU-stack,,@progbits\";) <
> include/config/kernel.release > include/linux/utsrelease.h.tmp; if [ -r
> include/linux/utsrelease.h ] && cmp -s include/linux/utsrelease.h
> include/linux/utsrelease.h.tmp; then rm -f
> include/linux/utsrelease.h.tmp; else echo ' UPD
> include/linux/utsrelease.h'; mv -f include/linux/utsrelease.h.tmp
> include/linux/utsrelease.h; fi'
> make: *** [include/linux/utsrelease.h] Error 2
I'd check /dev/null and make sure it's not a regular file this
happened to me a while back
- David Brown
next prev parent reply other threads:[~2006-12-31 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 17:25 Robin Cook
2006-12-31 18:27 ` David Brown [this message]
2006-12-31 20:02 ` Ken Moffat
2006-12-31 20:41 ` Robin Cook
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=9c21eeae0612311027p17737cc0q765aca18fe22fd38@mail.gmail.com \
--to=dmlb2000@gmail.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=rcook@wyrms.net \
/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®