From: "Wayne Christian" <wayne_christian@sbcglobal.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu with Kqemu on Fedora Core using GCC 4.0
Date: Tue, 10 May 2005 09:02:14 -0700 [thread overview]
Message-ID: <002301c55579$a9d6af30$0233a8c0@dharma.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 2667 bytes --]
For whatever it is worth I get the following errors trying to compile qemu with kqemu on a Fedora Core 3 system. This system has been modified to install Eciplse and GCC 4.0 from Fedora Core 4 test 2, but is otherwise a Fedora Core 3 system.
[root@WmainLinux qemu-0.7.0]# ./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 /usr/src/qemu-0.7.0
C compiler gcc
make make
host CPU i386
host big endian no
target list i386-user arm-user armeb-user sparc-user ppc-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu
gprof enabled no
static build no
SDL support no
mingw32 support no
Adlib support no
FMOD support no
kqemu support yes
KQEMU Linux module configuration:
kernel sources /lib/modules/2.6.11-1.7_FC3.desktop_3/build
kbuild type 2.6
[root@WmainLinux qemu-0.7.0]# make
for d in i386-user arm-user armeb-user sparc-user ppc-user i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu; do \
make -C $d all || exit 1 ; \
done
make[1]: Entering directory `/usr/src/qemu-0.7.0/i386-user'
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -mpreferred-stack-boundary=2 -falign-functions=0 -fno-gcse -fno-reorder-blocks -fno-optimize-sibling-calls -I. -I/usr/src/qemu-0.7.0/target-i386 -I/usr/src/qemu-0.7.0 -I/usr/src/qemu-0.7.0/linux-user -I/usr/src/qemu-0.7.0/linux-user/i386 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/usr/src/qemu-0.7.0/fpu -I/usr/src/qemu-0.7.0/slirp -c -o op.o /usr/src/qemu-0.7.0/target-i386/op.c
/usr/src/qemu-0.7.0/target-i386/ops_sse.h: In function 'op_pshufw_mmx':
/usr/src/qemu-0.7.0/target-i386/ops_sse.h:574: error: unable to find a register to spill in class 'GENERAL_REGS'
/usr/src/qemu-0.7.0/target-i386/ops_sse.h:574: error: this is the insn:
(insn:HI 18 17 19 0 /usr/src/qemu-0.7.0/target-i386/ops_sse.h:569 (set (strict_low_part (subreg:HI (reg/v:DI 63 [ r ]) 0))
(mem/s/j:HI (plus:SI (mult:SI (reg:SI 64)
(const_int 2 [0x2]))
(reg/v/f:SI 59 [ s ])) [0 <variable>._w S2 A16])) 41 {*movstricthi_1} (insn_list:REG_DEP_TRUE 16 (insn_list:REG_DEP_TRUE 12 (insn_list:REG_DEP_TRUE 53 (nil))))
(expr_list:REG_DEAD (reg:SI 64)
(nil)))
/usr/src/qemu-0.7.0/target-i386/ops_sse.h:574: confused by earlier errors, bailing out
make[1]: *** [op.o] Error 1
make[1]: Leaving directory `/usr/src/qemu-0.7.0/i386-user'
make: *** [all] Error 1
[root@WmainLinux qemu-0.7.0]#
[-- Attachment #2: Type: text/html, Size: 4055 bytes --]
next reply other threads:[~2005-05-10 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 16:02 Wayne Christian [this message]
2005-05-10 17:14 ` [Qemu-devel] Qemu with Kqemu on Fedora Core using GCC 4.0 Hetz Ben Hamo
2005-05-10 19:39 ` Fabrice Bellard
2005-05-10 21:48 ` Michael McConnell
2005-05-11 6:57 ` Christian MICHON
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='002301c55579$a9d6af30$0233a8c0@dharma.home' \
--to=wayne_christian@sbcglobal.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).