From: Chris Stromblad <chris.stromblad-yx4YqRIVDag@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: KVM-19 compile on Feisty Fawn fails
Date: Sat, 21 Apr 2007 10:22:22 +0200 [thread overview]
Message-ID: <1177143742.6342.1.camel@workstation> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2434 bytes --]
Hi there,
When attempting to compile KVM-19 I get the following error, anyone feel
like shedding some light on this? :)
/ Chris
chris@workstation:~/download/kvm-19$ ./configure
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /home/chris/download/kvm-19/qemu
C compiler /usr/bin/gcc-3.3
Host C compiler gcc
make make
install install
host CPU i386
host big endian no
target list i386-softmmu
gprof enabled no
profiler no
static build no
SDL support yes
SDL static link yes
mingw32 support no
Adlib support no
CoreAudio support no
ALSA support yes
DSound support no
FMOD support no
kqemu support no
kvm support yes
Documentation no
/home/chris/download/kvm-19/qemu/qemu-kvm.c: In function `load_regs':
/home/chris/download/kvm-19/qemu/qemu-kvm.c:254: error: unable to find a
register to spill in class `DIREG'
/home/chris/download/kvm-19/qemu/qemu-kvm.c:254: error: this is the
insn:
(insn:HI 65 588 67 2 0x4060f108 (parallel [
(set (reg:SI 2 ecx [80])
(const_int 0 [0x0]))
(set (reg/f:SI 0 eax [77])
(plus:SI (ashift:SI (reg:SI 2 ecx [79])
(const_int 2 [0x2]))
(reg/f:SI 252)))
(set (mem:BLK (reg/f:SI 252) [0 A8])
(const_int 0 [0x0]))
(use (reg:SI 0 eax [78]))
(use (reg:SI 2 ecx [79]))
(use (reg:SI 19 dirflag))
]) 459 {rep_stossi} (insn_list 576 (insn_list 61 (insn_list 62
(insn_list 63 (nil)))))
(expr_list:REG_DEAD (reg:SI 19 dirflag)
(expr_list:REG_DEAD (reg:SI 0 eax [78])
(expr_list:REG_DEAD (reg:SI 2 ecx [79])
(expr_list:REG_UNUSED (reg:SI 2 ecx [80])
(expr_list:REG_UNUSED (reg/f:SI 0 eax [77])
(nil)))))))
/home/chris/download/kvm-19/qemu/qemu-kvm.c:254: confused by earlier
errors, bailing out
make[2]: *** [qemu-kvm.o] Error 1
make[2]: Leaving directory
`/home/chris/download/kvm-19/qemu/i386-softmmu'
make[1]: *** [subdir-i386-softmmu] Error 2
make[1]: Leaving directory `/home/chris/download/kvm-19/qemu'
make: *** [qemu] Error 2
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #3: Type: text/plain, Size: 186 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next reply other threads:[~2007-04-21 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 8:22 Chris Stromblad [this message]
2007-04-21 9:06 ` KVM-19 compile on Feisty Fawn fails Carsten Emde
2007-04-21 14:59 ` Anthony Liguori
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=1177143742.6342.1.camel@workstation \
--to=chris.stromblad-yx4yqrivdag@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