From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=55185 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PjrB2-0002t5-21 for qemu-devel@nongnu.org; Mon, 31 Jan 2011 05:40:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PjrAx-0008Su-Vp for qemu-devel@nongnu.org; Mon, 31 Jan 2011 05:40:05 -0500 Received: from smtp.siriusit.co.uk ([81.187.123.5]:57346 helo=ra.servers.siriusit.co.uk) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PjrAx-0008QG-Fy for qemu-devel@nongnu.org; Mon, 31 Jan 2011 05:40:03 -0500 Received: from [192.168.1.137] (mcavea@[192.168.1.137]) by ra.servers.siriusit.co.uk (8.13.3/8.13.3) with ESMTP id p0VAeMft015893 for ; Mon, 31 Jan 2011 10:40:22 GMT Message-ID: <4D469179.9080705@siriusit.co.uk> Date: Mon, 31 Jan 2011 10:39:53 +0000 From: Mark Cave-Ayland MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] mingw32: Fix definitions for PRId64, PRIx64, PRIu64, PRIo64 References: <1291491689-11982-1-git-send-email-weil@mail.berlios.de> <4D45D7C6.70706@mail.berlios.de> <4D45DD13.2030303@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: qemu-devel@nongnu.org On 30/01/11 22:14, Blue Swirl wrote: > Well, mine doesn't. The change was introduced in mingw-runtime 3.15, > which was released in September 2008, but Debian still hasn't updated > from 3.13. Maybe other distros are not so lagging and someone who > wishes to build QEMU on Windows is not pampered with distro support > for MinGW anyway. Perhaps a configure time check should be added? FWIW anyone using MingW now should be using the new GCC 4.5 based builds with the associated runtime rather than anything that old. I suspect most people using MingW for anything serious will be doing this already. I think adding the configure check would be the best solution here. >> QEMU defines __USE_MINGW_ANSI_STDIO, and __mingw_vfprintf >> understands C9x standard length specifiers. > BTW, MinGW FAQ page http://www.mingw.org/wiki/FAQ still mentions that > %ll formats are not supported. Since MingW uses the MSVCRT then by default it won't accept %ll, but my understanding is that Stefan is correct, i.e. defining __USE_MINGW_ANSI_STDIO causes MingW to use an internal standards-compliant implementation instead of the in-built MSVCRT version that *does* understand these extras. HTH, Mark. -- Mark Cave-Ayland - Senior Technical Architect PostgreSQL - PostGIS Sirius Corporation plc - control through freedom http://www.siriusit.co.uk t: +44 870 608 0063 Sirius Labs: http://www.siriusit.co.uk/labs