From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Zhao, Yunfeng" <yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: build error
Date: Tue, 31 Jul 2007 09:59:16 +0300 [thread overview]
Message-ID: <46AEDDC4.10605@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A01D5AEBB-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Zhao, Yunfeng wrote:
>
> I met following compile errors while building latest kvm.
>
> [root@kvm-build kvm-userspace]# make
>
> make -C kernel
>
> make[1]: Entering directory `/workspace/tmp/kvm-userspace/kernel'
>
> make -C /lib/modules/2.6.22-rc4/build M=`pwd` "$@"
>
> make[2]: Entering directory
> `/usr/src/redhat/BUILD/kernel-2.6.22rc4g85f6038f'
>
> CC [M] /workspace/tmp/kvm-userspace/kernel/svm.o
>
> In file included from /workspace/tmp/kvm-userspace/kernel/kvm_svm.h:10,
>
> from /workspace/tmp/kvm-userspace/kernel/svm.c:17:
>
> /workspace/tmp/kvm-userspace/kernel/kvm.h:302: error: field
> ‘preempt_notifier’ has incomplete type
>
External module support got temporarily broken on 2.6.23-rc1 and
previous kernels due to the use of the new preempt notifiers core
functionality. I am working on emulating it for older kernels, but it
may take a bit (I have a patch but it doesn't work well at the moment).
Note that in any case, external modules can be slower than a native
build (i.e. build the kernel using kvm.git) as some pieces of core
functionality need to be emulated.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2007-07-31 6:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 2:16 build error Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01D5AEBB-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-31 6:59 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-11 3:19 Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A023647A6-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-11 14:20 ` Avi Kivity
[not found] ` <470E3126.9030401-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-11 14:31 ` Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02125F6A-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-11 14:35 ` Laurent Vivier
2007-10-11 14:37 ` Avi Kivity
[not found] ` <470E3532.3010002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-11 14:48 ` Zhao, Yunfeng
2007-10-18 2:07 Zhao, Yunfeng
2007-10-23 2:55 Build error Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02441266-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-23 7:08 ` Laurent Vivier
[not found] ` <471D9E04.9020105-6ktuUTfB/bM@public.gmane.org>
2007-10-23 8:06 ` Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02125FA5-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-23 8:12 ` Laurent Vivier
2007-10-23 8:39 ` Avi Kivity
2007-11-28 1:24 build error Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A026DEC64-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-11-28 8:37 ` Uri Lublin
[not found] ` <474D28B2.8000601-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-28 9:35 ` Neo Jia
[not found] ` <5d649bdb0711280135ocb94bc8wafd771fa46f8508b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-28 9:55 ` Avi Kivity
[not found] <4B3B7459.7070204@czero.it>
2010-01-03 2:09 ` Alexander Graf
2010-01-05 17:08 ` Marcelo Tosatti
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=46AEDDC4.10605@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=yunfeng.zhao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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