[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] exec.h with x86_64 = conflicting types?
From: |
Matthew Daniel |
Subject: |
[Qemu-devel] exec.h with x86_64 = conflicting types? |
Date: |
Tue, 08 Feb 2005 19:49:57 -0500 |
gcc -Wall -O2 -g -fno-strict-aliasing -falign-functions=0 -fno-reorder-blocks
-fno-optimize-sibling-calls -I. -I/usr/src/cvs/qemu/target-i386
-I/usr/src/cvs/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/usr/src/cvs/qemu/slirp -c -o op.o /usr/src/cvs/qemu/target-i386/op.c
In file included from /usr/src/cvs/qemu/target-i386/op.c:22:
/usr/src/cvs/qemu/target-i386/exec.h:380: warning: conflicting types for
built-in function 'lrintl'
In file included from /usr/src/cvs/qemu/target-i386/op.c:37:
/usr/src/cvs/qemu/target-i386/opreg_template.h: In function `op_movl_A0_EAX':
/usr/src/cvs/qemu/target-i386/opreg_template.h:23: error: structure has no
member named `t2'
Then that error about the structure having to member `t2' repeats itself
a LOT.
I am on FC3 (x86_64) with gcc (GCC) 3.4.3 20050124 (Red Hat 3.4.3-17)
and the latest qemu cvs update.
I configured as: ./configure --prefix=/usr --target-list=x86_64-softmmu
Any help would be appreciated,
-- /v\atthew
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] exec.h with x86_64 = conflicting types?,
Matthew Daniel <=