All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jody McIntyre <scjody@sun.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH] Fix compile error in arch/x86/kernel/syscall_64.c
Date: Wed, 03 Dec 2008 10:00:07 -0800	[thread overview]
Message-ID: <4936C927.3030504@zytor.com> (raw)
In-Reply-To: <20081202215154.GL29919@clouds>

Jody McIntyre wrote:
> 1965aae3c98397aad957412413c07e97b1bd4e64 broke compilation on one of my
> systems:
> 
>   CC      arch/x86/kernel/syscall_64.o
> arch/x86/kernel/syscall_64.c:27: error: array index in initializer exceeds array bounds
> arch/x86/kernel/syscall_64.c:27: error: (near initialization for ‘sys_call_table’)
> arch/x86/kernel/syscall_64.c:27: warning: excess elements in array initializer
> arch/x86/kernel/syscall_64.c:27: warning: (near initialization for ‘sys_call_table’)
> make[1]: *** [arch/x86/kernel/syscall_64.o] Error 1
> make: *** [arch/x86/kernel/syscall_64.o] Error 2
> 
> Reverting only the parts of the commit that change ASM_X86__UNISTD_64_H
> to _ASM_X86_UNISTD_64_H fixes the problem.  Patch below.
> 
> I have no idea what's going on here.  Compiler bug?
> 

Okay, this makes no sense whatsoever.  Could you send me the following:

a. the .config you're using;
b. what kernel headers do you have in /usr/include
   (if you installed the old ones with the broken header guards
   with "make headers_install", then your development environment
   is broken);
c. "make arch/x86/kernel/syscall_64.i".

	-hpa

  reply	other threads:[~2008-12-03 18:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 21:51 [PATCH] Fix compile error in arch/x86/kernel/syscall_64.c Jody McIntyre
2008-12-03 18:00 ` H. Peter Anvin [this message]
2008-12-03 19:50   ` Jody McIntyre
2008-12-03 20:17     ` H. Peter Anvin
2008-12-03 21:23       ` Jody McIntyre
2008-12-04 14:32 ` Arnd Bergmann
2008-12-04 19:07   ` Jody McIntyre
2008-12-04 19:12   ` H. Peter Anvin

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=4936C927.3030504@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=scjody@sun.com \
    --cc=tglx@linutronix.de \
    /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.