From: Matthew Daniel <matthew.daniel@oversightsystems.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] exec.h with x86_64 = conflicting types?
Date: Tue, 08 Feb 2005 19:49:57 -0500 [thread overview]
Message-ID: <1107910197.4949.38.camel@dhcp113.oversighttech.com> (raw)
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
reply other threads:[~2005-02-09 1:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1107910197.4949.38.camel@dhcp113.oversighttech.com \
--to=matthew.daniel@oversightsystems.com \
--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).