From: Avi Kivity <avi@redhat.com>
To: gao@schrodinger.com
Cc: kvm@vger.kernel.org
Subject: Re: KVM-87 compile failed
Date: Sun, 28 Jun 2009 12:13:22 +0300 [thread overview]
Message-ID: <4A473432.40303@redhat.com> (raw)
In-Reply-To: <200906252240.30600.gao@schrodinger.com>
On 06/26/2009 08:40 AM, gao@schrodinger.com wrote:
> Hi,
>
> Compiling KVM-87 failed with following error:
>
> make -C /lib/modules/2.6.29-gentoo-r5/build M=`pwd` \
> LINUXINCLUDE="-I`pwd`/include -Iinclude \
> -Iarch/x86/include -I`pwd`/include-compat \
> -include include/linux/autoconf.h \
> -include `pwd`/x86/external-module-compat.h " \
> "$@"
> CC [M] /tmp/kvm-87/kvm/kernel/x86/vmx.o
> /tmp/kvm-87/kvm/kernel/x86/vmx.c: In function ‘ept_rsvd_mask’:
> /tmp/kvm-87/kvm/kernel/x86/vmx.c:3272: error: ‘struct cpuinfo_x86’ has no
> member named ‘x86_phys_bits’
> make[4]: *** [/tmp/kvm-87/kvm/kernel/x86/vmx.o] Error 1
> make[3]: *** [/tmp/kvm-87/kvm/kernel/x86] Error 2
> make[2]: *** [_module_/tmp/kvm-87/kvm/kernel] Error 2
> make[1]: *** [all] Error 2
> make: *** [kvm-kmod] Error 2
>
> GCC-4.3.2-r3, kernel 2.6.29-gentoo-r5.
>
> Compiling worked fine with KVM-86.
>
>
kvm-87 is fairly compile-broken on 32-bit hosts. I need to improve my
compile testing infrastructure, or make the kvm-xx release candidate
process public.
You can work around it by replacing 'boot_cpu_data.x86_phys_bits' in
vmx.c by the constant 40.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-06-28 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 5:40 KVM-87 compile failed gao
2009-06-26 9:35 ` FinnTux
2009-06-28 9:13 ` 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=4A473432.40303@redhat.com \
--to=avi@redhat.com \
--cc=gao@schrodinger.com \
--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 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.