From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Fedora 4 + GCC4 + Qemu WAS: [patch] gcc4 host support
Date: Mon, 20 Jun 2005 13:18:45 +1200 [thread overview]
Message-ID: <1119230325.16281.2.camel@unixadmindazfc2.chh.co.nz> (raw)
In-Reply-To: <200506171402.54826.paul@codesourcery.com>
Aha! Ok, thanks for that. I have compiled Qemu OK now on FC4 with
gcc3.2.3 and compiled the accelerator module with gcc4.0 OK. The two
seem to work together fine so all is good :)
D
On Fri, 2005-06-17 at 14:02 +0100, Paul Brook wrote:
> On Friday 17 June 2005 13:58, Darryl Dixon wrote:
> > Oh,
> >
> > Sorry, obviously I badly misunderstood the nature of the patch that
> > you were posting; I assumed it was to enable Qemu to be compiled with
> > GCC4. That it can't is a pretty big downer; it basically means Qemu is
> > unusable on FC4 :( Ouch. C'est la vie :)
>
> Ah, I see what you mean. I did say in my original post
> "On x86 I've had to hack round other bugs..."
> Specifically http://gcc.gnu.org/PR16185
>
> Those hacks are way too ugly for me to want to make them public.
>
> You can get an older version of gcc (3.2.3) on FC4 by installing the
> compat-gcc packages.
>
> Paul
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
next prev parent reply other threads:[~2005-06-20 1:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 21:04 [Qemu-devel] [patch] gcc4 host support Paul Brook
2005-05-12 17:00 ` Paul Brook
2005-05-12 22:13 ` Pascal Terjan
2005-05-12 22:25 ` Paul Brook
2005-05-14 7:55 ` Filip Navara
2005-05-14 11:53 ` Paul Brook
2005-05-14 11:56 ` Filip Navara
2005-06-17 4:30 ` [Qemu-devel] Fedora 4 + GCC4 + Qemu WAS: " Darryl Dixon
2005-06-17 12:45 ` Paul Brook
[not found] ` <1119013084.5187.4.camel@darrylsfc3box>
2005-06-17 13:02 ` Paul Brook
2005-06-17 22:18 ` David Woodhouse
2005-06-20 1:18 ` Darryl Dixon [this message]
2005-05-16 9:41 ` [Qemu-devel] " David Woodhouse
2005-05-17 20:46 ` Paul Brook
2005-05-18 10:06 ` Herbert Poetzl
2005-05-18 16:02 ` Paul Brook
2005-05-18 16:10 ` David Woodhouse
2005-05-18 19:29 ` John Hogerhuis
2005-05-18 20:48 ` Paul Brook
2005-05-18 20:55 ` David Woodhouse
2005-05-18 21:16 ` Paul Brook
2005-05-18 21:29 ` jeebs
2005-05-18 22:37 ` Paul Brook
2005-05-18 23:05 ` Ian Rogers
2005-05-18 22:37 ` Ian Rogers
2005-05-19 7:23 ` Gwenole Beauchesne
2005-05-19 13:20 ` Paul Brook
2005-05-19 14:07 ` Gwenole Beauchesne
2005-05-19 15:44 ` Paul Brook
2005-05-19 18:14 ` Thomas Steffen
2005-05-19 18:52 ` Paul Brook
2005-05-19 19:38 ` Tim Walker
2005-05-19 19:45 ` Paul Brook
2005-05-19 21:03 ` Thomas Steffen
2005-05-19 22:25 ` John Hogerhuis
2005-05-20 9:59 ` Thomas Steffen
2005-05-20 12:57 ` Paul Brook
2005-05-19 16:18 ` Ian Rogers
2005-05-19 13:47 ` McMullan, Jason
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=1119230325.16281.2.camel@unixadmindazfc2.chh.co.nz \
--to=esrever_otua@pythonhacker.is-a-geek.net \
--cc=paul@codesourcery.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).