From: "jamesmikedupont@googlemail.com" <jamesmikedupont@googlemail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Build on i386
Date: Mon, 9 Nov 2009 15:39:46 +0100 [thread overview]
Message-ID: <ee9cc730911090639w3852b6d1k5c5bf3f31bfe5a92@mail.gmail.com> (raw)
Hi ,
I have patched the qemu to even build on i386. Now all the targets build,
but I cannot run all targets.
./i386-softmmu/qemu -L / /bin/ls
qemu: could not load PC BIOS 'bios.bin'
Does not work.
./i386-linux-user/qemu-i386 -L / /bin/ls
qemu: Unsupported syscall: 240
qemu: Unsupported syscall: 240
acl.c config-host.ld kvm-all.c posix-aio-compat.o
qemu-thread.c target-cris
acl.d config-host.mak kvm.h ppc64abi32-linux-user
qemu-thread.h target-i386
Works.
./x86_64-softmmu/qemu-system-x86_64 -L / /bin/ls
qemu: could not load PC BIOS 'bios.bin'
mdupont@introspector-desktop:~/2009/11/external/qemugit/mainline/qemu$
./x86_64-linux-user/qemu-x86_64 -L / /bin/ls
Error -8 while loading /bin/ls
diff --git a/configure b/configure
index aa2cc43..451c2be 100755
--- a/configure
+++ b/configure
@@ -1736,7 +1736,8 @@ if test "$debug" = "no" ; then
fi
QEMU_CFLAGS="-Wall -Wundef -Wendif-labels -Wwrite-strings
-Wmissing-prototypes $QEMU_CFLAGS"
QEMU_CFLAGS="-Wstrict-prototypes -Wredundant-decls $QEMU_CFLAGS"
-QEMU_CFLAGS="-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
$QEMU_CFLAGS"
+#QEMU_CFLAGS="-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE $QEMU_CFLAGS"
+QEMU_CFLAGS="-D_GNU_SOURCE -D_LARGEFILE_SOURCE $QEMU_CFLAGS"
QEMU_CFLAGS="-U_FORTIFY_SOURCE $QEMU_CFLAGS"
QEMU_CFLAGS="-I. -I\$(SRC_PATH) $QEMU_CFLAGS"
LDFLAGS="-g $LDFLAGS"
next reply other threads:[~2009-11-09 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 14:39 jamesmikedupont [this message]
2009-11-09 14:55 ` [Qemu-devel] Build on i386 Laurent Desnogues
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=ee9cc730911090639w3852b6d1k5c5bf3f31bfe5a92@mail.gmail.com \
--to=jamesmikedupont@googlemail.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).