From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51463 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Okkz8-0003lS-33 for qemu-devel@nongnu.org; Sun, 15 Aug 2010 17:43:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Okkz6-0005nD-JX for qemu-devel@nongnu.org; Sun, 15 Aug 2010 17:43:17 -0400 Received: from mail-gw0-f45.google.com ([74.125.83.45]:47212) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Okkz6-0005n9-FC for qemu-devel@nongnu.org; Sun, 15 Aug 2010 17:43:16 -0400 Received: by gwb11 with SMTP id 11so1848477gwb.4 for ; Sun, 15 Aug 2010 14:43:15 -0700 (PDT) Message-ID: <4C685F5D.2090707@codemonkey.ws> Date: Sun, 15 Aug 2010 16:42:53 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Unmaintained QEMU builds References: <4C62825A.6000903@mail.berlios.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: QEMU Developers On 08/11/2010 11:34 AM, Blue Swirl wrote: > On Wed, Aug 11, 2010 at 10:58 AM, Stefan Weil 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. > >