From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Andreas Färber" <andreas.faerber@web.de>
Subject: Re: [Qemu-devel] Still compile problems with TCG
Date: Wed, 27 Feb 2008 16:50:25 +0000 [thread overview]
Message-ID: <200802271650.26836.paul@codesourcery.com> (raw)
In-Reply-To: <99FB8BD3-4240-467F-8120-04A3FD200311@web.de>
On Wednesday 27 February 2008, Andreas Färber wrote:
> Am 27.02.2008 um 17:14 schrieb Paul Brook:
> >> I still have problems (Pentium M, gcc (GCC) 4.1.2 20061115
> >> (prerelease)
> >
> > gcc4 isn't supposed to work.
>
> And I thought that was the whole point in breaking non-x86 hosts!
In the long term, yes. However the gcc3 dependency will remain until the tcg
migration has been completed.
Paul
prev parent reply other threads:[~2008-02-27 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 10:23 [Qemu-devel] Still compile problems with TCG Johannes Schindelin
2008-02-27 16:14 ` Paul Brook
2008-02-27 16:33 ` Andreas Färber
2008-02-27 16:50 ` Paul Brook [this message]
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=200802271650.26836.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=andreas.faerber@web.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).