From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Michael Matz <matz@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] make qemu work with GCC 4
Date: Wed, 29 Aug 2007 17:55:05 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708291753520.28586@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291834260.23011@wotan.suse.de>
Hi,
On Wed, 29 Aug 2007, Michael Matz wrote:
> On Wed, 29 Aug 2007, Johannes Schindelin wrote:
>
> > > Thanks for your effor Michael! Now, I only hope, one of the patches
> > > that makes qemu gcc4 compliant are soon merged.
> >
> > Well, to throw a spanner in the works: this patch is the 4th patch along
> > the lines that I came about. None of them (AFAICT) was tested well
> > enough to be included in CVS. Indeed, the biggest problem seems to be
> > to make a patch that not only works on the machine of the poster, but on
> > other machines, too.
>
> Please? qemu with that patch builds on four architectures, and tests
> fine on two of them (including cross targets) and only because I haven't
> run it on the other two architectures yet.
Hey, I am not criticising you! Instead, I am thankful enough that I went
so far as to expose it with git.
> It might or might not need more patches than just mine (as I started
> from our package), but in that case they are independend of making qemu
> work with gcc 4, which is the only thing my patch is concerned about.
I already reported the non-compiling state of sparc-linux-user... Any
idea what I could do about it?
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-29 16:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 19:57 [Qemu-devel] [patch] make qemu work with GCC 4 Michael Matz
2007-08-29 8:41 ` Andreas Färber
2007-08-29 11:40 ` Michael Matz
2007-08-29 13:14 ` Andreas Färber
2007-08-29 13:30 ` Michael Matz
2007-08-29 13:59 ` Mulyadi Santosa
2007-08-29 14:11 ` Johannes Schindelin
2007-08-29 16:40 ` Michael Matz
2007-08-29 16:55 ` Johannes Schindelin [this message]
2007-08-29 18:09 ` Blue Swirl
2007-08-30 12:46 ` Carlo Marcelo Arenas Belon
2007-08-29 13:59 ` Johannes Schindelin
2007-08-29 14:13 ` Ronald
2007-08-29 14:19 ` Johannes Schindelin
2007-08-29 14:38 ` Andreas Färber
2007-08-29 14:27 ` Andreas Färber
2007-08-29 11:08 ` Johannes Schindelin
2007-08-29 11:46 ` Michael Matz
2007-08-29 12:40 ` Johannes Schindelin
2007-08-29 15:06 ` Paul Brook
2007-08-29 17:29 ` Michael Matz
2007-08-30 16:52 ` Michael Matz
2007-08-29 18:08 ` Anthony Liguori
2007-08-30 20:28 ` Thiemo Seufer
2007-08-31 13:31 ` Michael Matz
2007-08-31 14:17 ` Thiemo Seufer
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=Pine.LNX.4.64.0708291753520.28586@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=matz@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).