From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Unmaintained QEMU builds
Date: Sun, 15 Aug 2010 16:42:53 -0500 [thread overview]
Message-ID: <4C685F5D.2090707@codemonkey.ws> (raw)
In-Reply-To: <AANLkTinXC8r+13q5y9K+mvyNZPNbvycRq8p4FU5T+J1K@mail.gmail.com>
On 08/11/2010 11:34 AM, Blue Swirl wrote:
> On Wed, Aug 11, 2010 at 10:58 AM, Stefan Weil<weil@mail.berlios.de> wrote:
>
>> Hi,
>>
>> since several months, QEMU for Windows (and mingw32 cross builds)
>> no longer builds without error.
>>
> Not true for mingw32, it was building fine here until the latest commit.
>
>
>> I suspect that the same is true for QEMU on Darwin (lots of errors like
>> darwin-user/qemu.h:149: error: cast to pointer from integer of different
>> size),
>> but I'm not sure here because I have no valid Darwin test environment.
>> Maybe someone can test this.
>>
>> What about these environments? They have no maintainers.
>> Should they be marked as unsupported? Are they still used?
>> Or should they be removed?
>>
> I compile test mingw32 very often, it's part of my build test setup.
> If the build breaks, I may even fix the problem
>
But do you do any testing with the Windows build?
Historically, even when Windows builds, it spends large periods of time
not actually working. I think Stefan can confirm this. Much of the
platform specific code is way behind (like the block layer) and has been
for many years.
I can't remember the last time someone sent a Win32 enhancement for
platform code.
Given that it's known to have a lot of issues, I would suggest that we
schedule Windows host support for deprecation in 0.15. I would not
recommend that we remove any of the WIN32 code from the build but
basically stop trying to make it even build until someone steps up to
really actively maintain and enhance the Windows port. I would still
suggest we take patches if anyone wants to submit them but we should not
avoid patches that are known to break win32 (unless the fix is trivial).
For instance, I know that some downstreams (like Android) depend heavily
on Win32 so an official statement of deprecation might cause them to
push some of their fixes upstream and be more active in upstream
maintenance.
Regards,
Anthony Liguori
> But perhaps darwin-user should be removed.
>
>
next prev parent reply other threads:[~2010-08-15 21:43 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 10:58 [Qemu-devel] Unmaintained QEMU builds Stefan Weil
[not found] ` <AANLkTik+R8MZKL8LBgPUeNeCd9nL-wp94rm0MmMVqzWT@mail.gmail.com>
2010-08-11 11:10 ` Fwd: " Matthijs ter Woord
2010-08-11 16:34 ` Blue Swirl
2010-08-11 18:18 ` Stefan Weil
2010-08-11 18:51 ` Blue Swirl
2010-08-11 19:19 ` Blue Swirl
2010-08-11 19:37 ` Stefan Weil
2010-08-11 22:12 ` [Qemu-devel] " Paolo Bonzini
2010-08-12 9:17 ` Stefan Weil
2010-08-12 12:05 ` Paolo Bonzini
2010-08-17 8:19 ` Jes Sorensen
2010-08-15 9:48 ` [Qemu-devel] " Blue Swirl
2010-08-15 21:42 ` Anthony Liguori [this message]
2010-08-16 8:45 ` [Qemu-devel] " Paolo Bonzini
2010-08-16 18:51 ` [Qemu-devel] " Blue Swirl
2010-08-16 20:42 ` Anthony Liguori
2010-08-17 10:09 ` Kevin Wolf
2010-08-17 13:00 ` Anthony Liguori
2010-08-17 18:38 ` Blue Swirl
2010-08-17 18:49 ` malc
2010-08-17 19:56 ` Anthony Liguori
2010-08-18 8:31 ` [Qemu-devel] " Paolo Bonzini
2010-09-04 14:03 ` Andreas Färber
2010-09-05 15:41 ` Paolo Bonzini
2010-09-05 16:35 ` Andreas Färber
2010-08-18 9:46 ` [Qemu-devel] " Alexander Graf
2010-09-05 15:31 ` [Qemu-devel] " Paolo Bonzini
2010-09-04 13:56 ` [Qemu-devel] " Andreas Färber
2010-09-05 11:19 ` Avi Kivity
2010-09-05 14:10 ` Blue Swirl
2010-09-05 14:17 ` Avi Kivity
2010-09-05 14:40 ` Blue Swirl
2010-09-05 14:46 ` Avi Kivity
2010-09-05 15:44 ` Andreas Färber
2010-09-05 15:57 ` Avi Kivity
2010-09-05 15:01 ` Andreas Färber
2010-09-05 15:10 ` Avi Kivity
2010-09-05 15:57 ` Anthony Liguori
2010-09-05 16:05 ` Avi Kivity
2010-09-05 16:25 ` Blue Swirl
2010-09-05 16:31 ` Avi Kivity
2010-09-05 17:33 ` malc
2010-09-05 17:44 ` andrzej zaborowski
2010-09-05 17:51 ` Avi Kivity
2010-09-05 17:56 ` andrzej zaborowski
2010-09-05 17:57 ` Avi Kivity
2010-09-05 19:21 ` Edgar E. Iglesias
2010-09-05 19:27 ` Anthony Liguori
2010-09-05 17:39 ` Peter Maydell
2010-09-05 19:25 ` Anthony Liguori
2010-09-06 8:59 ` [Qemu-devel] " Paolo Bonzini
2010-09-06 9:33 ` Corentin Chary
2010-09-06 22:44 ` [Qemu-devel] " Andreas Färber
2010-09-07 7:38 ` Tristan Gingold
2010-09-07 10:22 ` Alexander Graf
2010-09-07 10:31 ` Tristan Gingold
2010-09-07 8:45 ` [Qemu-devel] " Paolo Bonzini
2010-09-04 14:41 ` [Qemu-devel] " Andreas Färber
2010-09-05 10:03 ` Alexander Graf
2010-09-05 17:54 ` [Qemu-devel] Unmaintained ppc features (was: Unmaintained QEMU builds) Andreas Färber
2010-08-14 15:22 ` [Qemu-devel] Unmaintained QEMU builds Andreas Färber
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=4C685F5D.2090707@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@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).