All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: David Brown <dmlb2000@gmail.com>
Cc: Robin Cook <rcook@wyrms.net>, Linux-kernel@vger.kernel.org
Subject: Re: compile failure on 2.6.19
Date: Sun, 31 Dec 2006 20:02:05 +0000	[thread overview]
Message-ID: <20061231200205.GA9055@deepthought> (raw)
In-Reply-To: <9c21eeae0612311027p17737cc0q765aca18fe22fd38@mail.gmail.com>

On Sun, Dec 31, 2006 at 10:27:26AM -0800, David Brown wrote:
> 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

 If that doesn't fix it, I suspect it's a shell problem (e.g.
bash-3.{1,2} without all the patches).  I've seen a number of
issues with bash in the past few months, sometimes it highlighted
code that needed to be fixed, other times it tripped over
parentheses.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  reply	other threads:[~2006-12-31 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31 17:25 compile failure on 2.6.19 Robin Cook
2006-12-31 18:27 ` David Brown
2006-12-31 20:02   ` Ken Moffat [this message]
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=20061231200205.GA9055@deepthought \
    --to=zarniwhoop@ntlworld.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=dmlb2000@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.