From: Michael Matz <matz@suse.de>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [patch] make qemu work with GCC 4
Date: Wed, 29 Aug 2007 15:30:45 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708291524560.23011@wotan.suse.de> (raw)
In-Reply-To: <49F27907-6C55-40D8-A6FF-7769156F8E74@web.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1438 bytes --]
Hi,
On Wed, 29 Aug 2007, Andreas Färber wrote:
> > >What do you mean with 0.9.0-cvs? The 0.9.0 GCC4 patches for OSX/Intel
> >
> >Do you mean my patches?
>
> No. Are yours already OSX-compatible?
No OSX, no idea :)
> I referred to previous patches, specifically those currently applied for
> Q: http://www.kju-app.org/proj/browser/trunk/patches There were also
> some in the QEMU forums. Those only apply to the 0.9.0 tag.
I see. We seem to use some of these patches (perhaps in a modified form)
in our qemu package too. Sorry that I'm so unsure about the qemu topics,
I'm only a compiler developer hitting qemu hard enough until it works with
gcc4 :-)
> So I was wondering whether 0.9.0-cvs from date meant 0.9.0 tag or HEAD
> as of date.
It was supposed to mean some CVS checkout from after 0.9.0 release, where
I myself couldn't really make out at which date the checkout was done
(because it wasn't done by me, and I didn't feel like digging too long, as
the patch obviously still applied mostly).
> Sorry if this is obvious but I'm used to Subversion. In your patch I
> first read qemu-0.9.0, which confused me as I don't consider CVS HEAD to
> be 0.9.0. Will try your updated patch later.
That btw. is against CVS HEAD (as of today). I have no idea what's
necessary for OSX, it might be that you need additional patches, or not,
can't help with that.
Ciao,
Michael.
next prev parent reply other threads:[~2007-08-29 13:30 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 [this message]
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
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.0708291524560.23011@wotan.suse.de \
--to=matz@suse.de \
--cc=agraf@suse.de \
--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).