From: Magnus Damm <magnus.damm@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] win32 build broken
Date: Thu, 6 Jan 2005 23:52:43 +0100 [thread overview]
Message-ID: <aec7e5c3050106145253b28ecb@mail.gmail.com> (raw)
In-Reply-To: <20050106223507.GG23549@cs.unibo.it>
On Thu, 6 Jan 2005 23:35:07 +0100, Renzo Davoli <renzo@cs.unibo.it> wrote:
> I have the same problem on linuxppc (also using tonight cvs updates).
Speaking of linuxppc...
Have you tried the improved softmmu patches on a ppc host?
/ magnus
next prev parent reply other threads:[~2005-01-06 23:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 13:03 [Qemu-devel] win32 build broken Ronald
2005-01-04 20:55 ` René Korthaus
2005-01-06 22:35 ` Renzo Davoli
2005-01-06 22:52 ` Magnus Damm [this message]
2005-01-07 7:37 ` [Qemu-devel] softmmu ppc Laurent Amon
2005-01-07 9:43 ` Daniel Egger
2005-01-07 12:06 ` Magnus Damm
2005-01-07 14:05 ` Piotras
2005-01-07 16:05 ` Daniel Egger
2005-01-08 9:57 ` Magnus Damm
2005-01-08 12:49 ` Daniel Egger
2005-01-08 21:47 ` [Qemu-devel] Re: win32 build broken Ronald
2005-01-08 22:12 ` Filip Navara
2005-01-08 22:37 ` [Qemu-devel] " Ronald
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=aec7e5c3050106145253b28ecb@mail.gmail.com \
--to=magnus.damm@gmail.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).