All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darrin Ritter <darrinritter@optusnet.com.au>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] trouble compiling om x86_64
Date: Mon, 24 Oct 2005 17:24:49 +0930	[thread overview]
Message-ID: <435C9349.5070909@optusnet.com.au> (raw)

hi
first of all sorry if this is posted on the wrong forum as I tried to 
join the user forum and got a 404 error

I have been using the qemu binary file on my FC4 machine without a hitch 
and now I am trying to compile on an amd 64 machine so i can get kqemu 
working.
I downloaded the files :

qemu-0.7.2.tar.gz <http://fabrice.bellard.free.fr/qemu/qemu-0.7.2.tar.gz>

kqemu-0.7.2.tar.gz <http://fabrice.bellard.free.fr/qemu/kqemu-0.7.2.tar.gz>

and then unpacked qemu into a directory then cd into the qemu directory 
and unpacked the kqemu with tar -zxvf ../kqemu-0.7.2.tar.gz.


I then did ./configure --target-list=i386-user , as I only really wanted 
i386 virtual machine and I go the following output:

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/dv/tmp/qemu-0.7.2
C compiler gcc
Host C compiler gcc
make make
host CPU x86_64
host big endian no
target list i386-user
gprof enabled no
static build no
SDL support yes
SDL static link yes
mingw32 support no
Adlib support no
FMOD support no
kqemu support yes

KQEMU Linux module configuration:
kernel sources /lib/modules/2.6.12-1.1398_FC4/build
kbuild type 2.6


when I ran make I go the following output error:

gcc -Wall -O2 -g -fno-strict-aliasing -falign-functions=0 
-fno-reorder-blocks -fno-optimize-sibling-calls -I. 
-I/home/dv/tmp/qemu-0.7.2/target-i386 -I/home/dv/tmp/qemu-0.7.2 
-I/home/dv/tmp/qemu-0.7.2/linux-user 
-I/home/dv/tmp/qemu-0.7.2/linux-user/i386 -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/dv/tmp/qemu-0.7.2/fpu 
-I/home/dv/tmp/qemu-0.7.2/slirp -c -o op.o 
/home/dv/tmp/qemu-0.7.2/target-i386/op.c
In file included from /home/dv/tmp/qemu-0.7.2/target-i386/op.c:22:
/home/dv/tmp/qemu-0.7.2/target-i386/exec.h: In function ‘helper_fldt’:
/home/dv/tmp/qemu-0.7.2/target-i386/exec.h:477: warning: cast to pointer 
from integer of different size
/home/dv/tmp/qemu-0.7.2/target-i386/exec.h: In function ‘helper_fstt’:
/home/dv/tmp/qemu-0.7.2/target-i386/exec.h:482: warning: cast to pointer 
from integer of different size
/home/dv/tmp/qemu-0.7.2/target-i386/op.c: In function ‘op_goto_tb0’:
/home/dv/tmp/qemu-0.7.2/target-i386/op.c:1300: warning: cast to pointer 
from integer of different size
/home/dv/tmp/qemu-0.7.2/target-i386/op.c: In function ‘op_goto_tb1’:
/home/dv/tmp/qemu-0.7.2/target-i386/op.c:1305: warning: cast to pointer 
from integer of different size
../dyngen -o op.h op.o
dyngen: ret or jmp expected at the end of op_bsfw_T0_cc
make[1]: *** [op.h] Error 1
make[1]: Leaving directory `/home/dv/tmp/qemu-0.7.2/i386-user'
make: *** [all] Error 1


what do I do to get the program to compile?

thanks Darrin

             reply	other threads:[~2005-10-24  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24  7:54 Darrin Ritter [this message]
2005-10-24  9:54 ` [Qemu-devel] trouble compiling om x86_64 Jan Marten Simons
2005-10-24 13:35   ` Darrin Ritter
2005-10-24 11:22 ` Darrin Ritter

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=435C9349.5070909@optusnet.com.au \
    --to=darrinritter@optusnet.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.