From: David Duardo <dduardo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: KVM-16 compiled against GCC 4
Date: Mon, 19 Mar 2007 11:18:06 -0400 [thread overview]
Message-ID: <45FEA9AE.5090206@gmail.com> (raw)
There seems to be a bug in the generated file qemu/i386-softmmu/op.h
when compiling kvm-16 against GCC 4.
If you apply the two GCC 4 patches to the kvm-16 source:
1) http://www.busybox.net/downloads/qemu/qemu-gcc-4-all.patch
2) http://www.kju-app.org/proj/browser/trunk/patches/qemu-0.9.0-gcc4.patch
and try to compile against GCC 4 you'll get a symbol redefinition error.
The solution is to remove all "extern char mempy;" lines in
qemu/i386-softmmu/op.h
So far kvm has been running very stable with the only problem being the
known reboot bug.
My question is where exactly is qemu/i386-softmmu/op.h being generated?
I want to patch the problem before it gets generated.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-03-19 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 15:18 David Duardo [this message]
[not found] ` <45FEA9AE.5090206-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-03-19 15:32 ` KVM-16 compiled against GCC 4 Anthony Liguori
[not found] ` <45FEAD12.2020604-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-03-19 15:48 ` Anthony Liguori
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=45FEA9AE.5090206@gmail.com \
--to=dduardo-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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