public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Lambeck <adrian-xXM4Y/USaS3ucvZx32VAuQ@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: compiling kvm-30
Date: Thu, 19 Jul 2007 16:26:55 +0200	[thread overview]
Message-ID: <469F74AF.8050907@basicsedv.de> (raw)

Hello everybody,
I reported compilation problems on linux-2.6.21.4 last week with kvm-29. 
These problems do not
occure with kvm-30. Instead the messages belo are now shown during 
compilation which make kvm unusable to me :-(.

Thanks for any solutions to this issue!


#########################################################
In file included from /root/kvm/kvm-30/kernel/kvm_svm.h:10,
                 from /root/kvm/kvm-30/kernel/svm.c:17:
/root/kvm/kvm-30/kernel/kvm.h: In function 'is_paging':
/root/kvm/kvm-30/kernel/kvm.h:648: error: 'X86_CR0_PG' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/kvm.h:648: error: (Each undeclared identifier is 
reported only once
/root/kvm/kvm-30/kernel/kvm.h:648: error: for each function it appears in.)
/root/kvm/kvm-30/kernel/svm.c: In function 'get_addr_size':
/root/kvm/kvm-30/kernel/svm.c:101: error: 'X86_CR0_PE' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c: In function 'init_vmcb':
/root/kvm/kvm-30/kernel/svm.c:565: error: 'X86_CR0_PG' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c:565: error: 'X86_CR0_WP' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c: In function 'svm_set_cr0':
/root/kvm/kvm-30/kernel/svm.c:769: error: 'X86_CR0_TS' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c:775: error: 'X86_CR0_PG' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c:775: error: 'X86_CR0_WP' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c:776: error: 'X86_CR0_CD' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c:776: error: 'X86_CR0_NW' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c: In function 'nm_interception':
/root/kvm/kvm-30/kernel/svm.c:947: error: 'X86_CR0_TS' undeclared (first 
use in this function)
/root/kvm/kvm-30/kernel/svm.c: In function 'svm_set_cr3':
/root/kvm/kvm-30/kernel/svm.c:1704: error: 'X86_CR0_TS' undeclared 
(first use in this function)
make[3]: *** [/root/kvm/kvm-30/kernel/svm.o] Error 1
make[2]: *** [_module_/root/kvm/kvm-30/kernel] Error 2
make[1]: *** [all] Error 2
make: *** [kernel] Error 2
make: *** Waiting for unfinished jobs....
/root/kvm/kvm-30/qemu/migration.c: In function `migrate_finish':
/root/kvm/kvm-30/qemu/migration.c:180: warning: implicit declaration of 
function `bdrv_flush_all'
/root/kvm/kvm-30/qemu/migration.c: In function `tcp_release':
/root/kvm/kvm-30/qemu/migration.c:683: warning: long int format, ssize_t 
arg (arg 3)
/root/kvm/kvm-30/qemu/migration.c:693: warning: long int format, ssize_t 
arg (arg 3)
/root/kvm/kvm-30/qemu/migration.c: In function `migrate_incoming_tcp':
/root/kvm/kvm-30/qemu/migration.c:915: warning: long int format, ssize_t 
arg (arg 3)
/root/kvm/kvm-30/qemu/migration.c:933: warning: long int format, ssize_t 
arg (arg 3)
/root/kvm/kvm-30/qemu/hw/apic.c: In function `apic_init_ipi':
/root/kvm/kvm-30/qemu/hw/apic.c:404: warning: implicit declaration of 
function `kvm_apic_init'
/root/kvm/kvm-30/qemu/hw/apic.c: In function `apic_startup':
/root/kvm/kvm-30/qemu/hw/apic.c:420: warning: implicit declaration of 
function `kvm_update_after_sipi'
/root/kvm/kvm-30/qemu/hw/acpi.c: In function `piix4_pm_init':
/root/kvm/kvm-30/qemu/hw/acpi.c:476: warning: unused variable `pm_io_base'
/root/kvm/kvm-30/qemu/exec.c: In function `cpu_breakpoint_insert':
/root/kvm/kvm-30/qemu/exec.c:1055: warning: implicit declaration of 
function `kvm_update_debugger'
/root/kvm/kvm-30/qemu/exec.c: In function `cpu_interrupt':
/root/kvm/kvm-30/qemu/exec.c:1146: warning: implicit declaration of 
function `kvm_update_interrupt_request'
/root/kvm/kvm-30/qemu/exec.c: In function 
`cpu_physical_memory_set_dirty_tracking':
/root/kvm/kvm-30/qemu/exec.c:1440: warning: implicit declaration of 
function `kvm_physical_memory_set_dirty_tracking'
/root/kvm/kvm-30/qemu/qemu-kvm.c: In function `kvm_main_loop_cpu':
/root/kvm/kvm-30/qemu/qemu-kvm.c:663: warning: implicit declaration of 
function `qemu_system_reset'
/root/kvm/kvm-30/qemu/target-i386/helper.c: In function `do_interrupt64':
/root/kvm/kvm-30/qemu/target-i386/helper.c:847: warning: implicit 
declaration of function `exit'
/root/kvm/kvm-30/qemu/target-i386/helper2.c: In function `cpu_x86_init':
/root/kvm/kvm-30/qemu/target-i386/helper2.c:156: warning: implicit 
declaration of function `kvm_qemu_init_env'


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

             reply	other threads:[~2007-07-19 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 14:26 Adrian Lambeck [this message]
     [not found] ` <469F74AF.8050907-xXM4Y/USaS3ucvZx32VAuQ@public.gmane.org>
2007-07-19 14:44   ` compiling kvm-30 Avi Kivity

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=469F74AF.8050907@basicsedv.de \
    --to=adrian-xxm4y/usas3ucvzx32vauq@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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