From: Bob Deblier <bob.deblier@telenet.be>
To: Qemu-devel@nongnu.org
Subject: [Qemu-devel] Linux x86_64 host
Date: Thu, 07 Oct 2004 15:42:33 +0200 [thread overview]
Message-ID: <1097156553.2833.17.camel@orion> (raw)
Great project!
I've been trying to see if I can get the current CVS version of QEMU
working on my Fedora Core 2 x86_64, with no luck so far. There's even a
compilation error in the current sparc code:
../dyngen -o op.h op.o
../dyngen -c -o opc.h op.o
gcc -Wall -O2 -g -fno-strict-aliasing -I.
-I/home/bob/emulators/cvs/qemu/target-sparc
-I/home/bob/emulators/cvs/qemu -I/home/bob/emulators/cvs/qemu/linux-user
-I/home/bob/emulators/cvs/qemu/linux-user/sparc -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/home/bob/emulators/cvs/qemu/slirp -c -o translate-all.o
/home/bob/emulators/cvs/qemu/translate-all.c
In file included from /home/bob/emulators/cvs/qemu/translate-all.c:41:
op.h: In function `dyngen_code':
op.h:4639: error: syntax error before '.' token
op.h:4641: error: syntax error before '.' token
make[1]: *** [translate-all.o] Error 1
make[1]: Leaving directory `/home/bob/emulators/cvs/qemu/sparc-user'
I'm more than willing to make some time getting to know the system and
contributing to make this work on x86_64, if somebody can give pointers
on where to start investigating.
I've got many years experience programming, knowledge of several
varieties of assembler (x86, x86_64, ppc, ppc64, sparcv8/9, arm, ia64 -
as used in the BeeCrypt crypto library).
Sincerely,
Bob Deblier
next reply other threads:[~2004-10-07 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 13:42 Bob Deblier [this message]
2004-10-07 15:07 ` [Qemu-devel] Linux x86_64 host Johannes Schindelin
2004-10-07 15:25 ` Bob Deblier
2004-10-07 16:16 ` Johannes Schindelin
2004-10-07 18:37 ` Bob Deblier
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=1097156553.2833.17.camel@orion \
--to=bob.deblier@telenet.be \
--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).