From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>, nikola.ciprich@linuxbox.cz
Subject: Re: [ANNOUNCE] qemu-kvm-0.12.1
Date: Mon, 21 Dec 2009 14:33:13 +0200 [thread overview]
Message-ID: <4B2F6B09.9050302@redhat.com> (raw)
In-Reply-To: <20091220165704.GB9758@nik-comp.linuxbox.cz>
On 12/20/2009 06:57 PM, Nikola Ciprich wrote:
> Hi Avi,
> I just tried compiling and the same problem I've reported minutes ago:
> gcc -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1/slirp -m64 -Wold-style-definition -I. -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1 -U_FORTIFY_SOURCE -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -O2 -g -pipe -Wall -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DHAS_AUDIO -DHAS_AUDIO_CHOICE -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1/fpu -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1/tcg -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1/tcg/x86_64 -I.. -I/usr/src/redhat/BUILD/qemu-kvm-0.12.1/target-mips -DNEED_CPU_H -O2 -g -Wl,--warn-common -m64 -g -o qemu-system-mipsel vl.o async.o monitor.o pci.o pci_host.o pcie_host.o machine.o gdbstub.o virt
io-blk.o virtio-balloon.o virtio-net.o virtio-console.o virtio-pci.o msix.o isa_mmio.o eepro100.o pcnet.o rtl8139.o e1000.o mips_r4k.o mips_jazz.o mips_malta.o mips_mipssim.o mips_timer.o mip!
> s_int.o dma.o vga.o serial.o i8254.o i8259.o rc4030.o vga-pci.o vga-isa.o vga-isa-mm.o g364fb.o jazz_led.o dp8393x.o ide/core.o ide/qdev.o ide/isa.o ide/pci.o ide/piix.o gt64xxx.o pckbd.o fdc.o mc146818rtc.o usb-uhci.o acpi.o ds1225y.o piix4.o parallel.o cirrus_vga.o pcspk.o sb16.o es1370.o ac97.o mipsnet.o ne2000-isa.o pflash_cfi01.o vmware_vga.o -Wl,--whole-archive ../libqemu_common.a libqemu.a ../libhw64/libqemuhw64.a -Wl,--no-whole-archive -lrt -lpthread -lutil -lpci -lz -lbluetooth -L/usr/kerberos/lib64 -lcurl -ldl -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lidn -lssl -lcrypto -lz -lncurses -lasound -luuid -lsasl2 -lgnutls -L/usr/lib64 -lSDL -lpthread -lX11 -lm -lz
> monitor.o: In function `mon_get_cpu':
> /usr/src/redhat/BUILD/qemu-kvm-0.12.1/monitor.c:680: undefined reference to `kvm_save_mpstate'
> monitor.o: In function `do_info_cpus':
> /usr/src/redhat/BUILD/qemu-kvm-0.12.1/monitor.c:783: undefined reference to `kvm_save_mpstate'
>
I've fixed this for 0.12.2 (or 0.12.1.1, depends).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-21 12:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 16:40 [ANNOUNCE] qemu-kvm-0.12.1 Avi Kivity
2009-12-20 16:57 ` Nikola Ciprich
2009-12-20 22:06 ` Alexander Graf
2009-12-21 6:33 ` Nikola Ciprich
2009-12-21 12:19 ` Avi Kivity
2009-12-21 12:33 ` Avi Kivity [this message]
2009-12-21 13:17 ` Nikola Ciprich
2009-12-21 5:58 ` John Wong
2009-12-21 14:43 ` Thomas Mueller
2009-12-21 15:44 ` John Wong
2009-12-21 16:46 ` FinnTux
2009-12-21 8:14 ` Ingmar Schraub
2009-12-21 8:41 ` Ingmar Schraub
2009-12-21 9:43 ` Thomas Mueller
2009-12-21 9:58 ` Ingmar Schraub
2009-12-21 14:48 ` Avi Kivity
2009-12-21 15:39 ` Ingmar Schraub
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=4B2F6B09.9050302@redhat.com \
--to=avi@redhat.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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