public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: kvm@vger.kernel.org
Subject: Re: compiling with icc: kvm.h(240): error
Date: Sun, 09 Nov 2008 17:00:04 +0200	[thread overview]
Message-ID: <4916FAF4.2010806@redhat.com> (raw)
In-Reply-To: <4900AD7F.6030606@nagafix.co.uk>

Antoine Martin wrote:
> Hi,
>
> I am testing kernel builds with Intel's ICC and got a failure on KVM 
> (not that the rest was very smooth either...)
> Just in case someone is interested, here it is (this kernel tree is 
> loosely based on linux-next + other patches):
>
> CC [M]  arch/x86/kvm/svm.o - due to: include/linux/bounds.h
> icc -Wp,-MD,arch/x86/kvm/.svm.o.d -nostdinc -isystem icc 
> -I/usr/lib/gcc/i486-pc-linux-gnu/4.3.2/include -D__KERNEL__ -Iinclude 
> -I/usr/src/fastboot.git/arch/x86/include -include 
> include/linux/autoconf.h -Wall    -fno-strict-aliasing -fno-common 
> -Werror-implicit-function-declaration -Os -m32   -freg-struct-return  
> -mtune=generic  -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 
> -pipe   -Iinclude/asm-x86/mach-default   -fno-omit-frame-pointer   
> -Ivirt/kvm -Iarch/x86/kvm -DMODULE -DKBUILD_STR(s)=#s 
> -DKBUILD_BASENAME=KBUILD_STR(svm) -DKBUILD_MODNAME=KBUILD_STR(kvm_amd) 
> -c -o arch/x86/kvm/.tmp_svm.o arch/x86/kvm/svm.c
> icc: command line warning #10156: ignoring option '-W'; no argument 
> required
> include/linux/kvm.h(240): error: "padding" has already been declared 
> in the current scope
>               __u64 padding;
>                     ^
>

Please resend with a changelog entry and signoff.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2008-11-09 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 16:59 compiling with icc: kvm.h(240): error Antoine Martin
2008-11-09 15:00 ` Avi Kivity [this message]

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=4916FAF4.2010806@redhat.com \
    --to=avi@redhat.com \
    --cc=antoine@nagafix.co.uk \
    --cc=kvm@vger.kernel.org \
    /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