From: "Steve D. Perkins" <lists@steveperkins.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch Submission] QEMU with GCC/Win32
Date: Sat, 30 Jul 2005 15:41:23 -0400 [thread overview]
Message-ID: <42EBD7E3.7090409@steveperkins.net> (raw)
In-Reply-To: <200507302013.22433.paul@codesourcery.com>
Paul Brook wrote:
>Are you sure you included the correct patch?
>
>I don't see anything win32 specific about this patch. AFAICS it's just the
>gcc4 patch *that I wrote* and posed some time ago.
>Both cygwin and mingw is still using gcc3.4.x, so it shouldn't be necessary.
>
>
>
Paul -
Please don't think I'm trying to "plagiarize" or steal anyone else's
credit. I've been talking about this patch for some time, in posts to
the QEMU forum at "http://qemu.dad-answers.com/" and in the "Applying
windows source patch to CVS?" post to this mailing list on 7/27. When I
was trying to build QEMU 0.7.0, I found a patch at
"http://www.h7.dion.ne.jp/~qemu-win/PortingTips-en.html" for the 0.6
codebase... and I made a few modifications to it for 0.7.0. Yesterday,
I went through the same exercise to update it for QEMU 0.7.1. I've
changed some of the calls to the "error()" function in "dyngen.c", but
otherwise the main patch content remains the same.
I've been very up-front about the origins of the patch, and haven't
tried to pass myself off as the original author. However, the original
author hasn't posted an updated patch since the 0.6 generation of QEMU,
so you could say I've "adopted" and kept it maintained for the past two
QEMU releases. My INITIAL desire, before I started, was to contact the
original patch author and ask him/her to update it... but the website
listed above includes no names or contact information at all. Believe
me, I am NOT looking to be "The Official GCC/Win32 Guy" and continue
maintaining this patch forever... my ideal wish is for the changes to go
into the main codebase so future patching isn't necessary for anybody!
I'm not sure what you mean about the patch "not being necessary". I
haven't tried building with Cygwin, so I can't speak for that platform.
My build environment is MinGW with the MSYS shell (to avoid onerous
licensing issues and DLL dependencies), and I can assure that the patch
very much is necessary for the current release of QEMU with the current
release of MinGW. QEMU does compile fine on Win32 with GCC 3.4, but the
executable crashes immediately when you try to run it. By applying the
patch I just posted, you get an executable that compiles and runs
properly (I've been running a FreeBSD environment just fine with a build
from the 0.7.1 patch I just posted).
I get the impression that QEMU is not really being tested on the
Win32/GCC platform, so the team (is there a "team" or is it really just
Fabrice?) may not be aware that support is still lacking for that
platform. Unfortunately, that is the case... but the patch I just
posted corrects the issue, and that's why I'm encouraging its inclusion
in the main codebase.
Steve
next prev parent reply other threads:[~2005-07-30 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 18:42 [Qemu-devel] [Patch Submission] QEMU with GCC/Win32 Steve D. Perkins
2005-07-30 19:13 ` Paul Brook
2005-07-30 19:41 ` Steve D. Perkins [this message]
2005-07-30 21:16 ` Filip Navara
2005-07-30 21:28 ` Christian MICHON
2005-07-30 23:04 ` Steve D. Perkins
2005-07-30 23:04 ` Paul Brook
2005-07-30 23:16 ` Steve D. Perkins
2005-07-30 23:39 ` Paul Brook
2005-08-01 11:34 ` Gwenole Beauchesne
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=42EBD7E3.7090409@steveperkins.net \
--to=lists@steveperkins.net \
--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).