From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] build failure on x86, any suggestions?
Date: Sat, 15 Mar 2008 19:25:41 +0100 [thread overview]
Message-ID: <47DC14A5.2050806@mail.berlios.de> (raw)
In-Reply-To: <200803151420.25502.paul@codesourcery.com>
Paul Brook schrieb:
> 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.
>
> 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.
>
> 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".
>
> Paul
Hi Paul,
I got two similar error messages from other users. Both were using gcc-3.4,
one of them from ubuntu 7.10 (32bit). My own system had no problems
compiling exactly the same version with Debian lenny (amd64) gcc-3.4.
Stefan
next prev parent reply other threads:[~2008-03-15 18:26 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
[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 [this message]
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=47DC14A5.2050806@mail.berlios.de \
--to=weil@mail.berlios.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).