From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] build failure on x86, any suggestions?
Date: Sat, 15 Mar 2008 20:45:08 +0100 [thread overview]
Message-ID: <47DC2744.9090602@suse.de> (raw)
In-Reply-To: <1205593982.24804.78.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
Peter Volkov wrote:
> В Сбт, 15/03/2008 в 14:20 +0000, Paul Brook пишет:
>
>> On Saturday 15 March 2008, Peter Volkov wrote:
>>
>>> Hello.
>>>
>>> I just wanted to point developers attention to the following bug:
>>> bugs.gentoo.org/212351 , comment #11 and further. The problem is that
>>> qemu does not compile any more on x86. I've tried recent snapshot
>>> (2008-03-15_05) and the problem persist there.
>>>
>> You're almost certainly using gcc4.x. Don't do that.
>>
>
> Paul, thank you for you answer. I do have gcc-4 installed on my system
> but I'm sure that I'm using gcc-3.4:
>
>
>> gcc --version
>>
> gcc (GCC) 3.4.6 (Gentoo 3.4.6-r2 p1.5, ssp-3.4.6-1.0, pie-8.7.10)
>
> As I read FAQ this version should be supported. I've tried to build gcc
> without patches (ssp, pie, C++ support and some gentoo specific patches)
> but qemu build process still fails at the same place...
>
>
>> IIRC gentoo already has a big pile hacks for this. This kind of breakage is
>> exactly why those hacks haven't been merged into cvs. They're papering over
>> the problem rather than fixing it, so you should expect them to need constant
>> maintenance.
>>
>
> Sorry, but what hacks are you talking about? The only hack I'm aware
> about is that all system is build with newer compiler while to build
> qemu I have to install old gcc.
>
>
>> As mentioned several times on this recently on this list, the proper fix is to
>> finish the TCG conversion. That will happen "when it's done".
>>
>
> Eh, I saw you talking about this and I'm aware that this will definitely
> take time. That's why I asked for suggestion...
>
>
For the time being you could try the appended patch. It makes x86 on x86
slower though, but should enable you to have a working build at all. I
am not 100% sure if it actually does help in your case though.
Alex
[-- Attachment #2: qemu-reghack.patch --]
[-- Type: text/x-patch, Size: 258 bytes --]
--- a/target-i386/op.c
+++ b/target-i386/op.c
@@ -18,7 +18,7 @@
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*/
-#define ASM_SOFTMMU
+//#define ASM_SOFTMMU
#include "exec.h"
/* n must be a constant to be efficient */
next prev parent reply other threads:[~2008-03-15 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 14:01 [Qemu-devel] build failure on x86, any suggestions? Peter Volkov
2008-03-15 14:20 ` Paul Brook
2008-03-15 15:13 ` Peter Volkov
2008-03-15 19:45 ` Alexander Graf [this message]
[not found] ` <200803151150.06813.computers57@hotmail.com>
[not found] ` <200803160001.52124.computers57@hotmail.com>
2008-03-16 6:01 ` C.W. Betts
2008-03-16 13:11 ` Peter Volkov
2008-03-16 16:20 ` Blue Swirl
[not found] ` <200803191436.55827.computers57@hotmail.com>
2008-03-19 20:36 ` C.W. Betts
2008-03-15 18:25 ` Stefan Weil
2008-03-15 20:35 ` Blue Swirl
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=47DC2744.9090602@suse.de \
--to=agraf@suse.de \
--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).