From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] mingw32: Fix definitions for PRId64, PRIx64, PRIu64, PRIo64
Date: Mon, 31 Jan 2011 10:39:53 +0000 [thread overview]
Message-ID: <4D469179.9080705@siriusit.co.uk> (raw)
In-Reply-To: <AANLkTi=9SXp4QqAtW2p9hRzRqK8htrKx-GPWy_HAegsY@mail.gmail.com>
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
next prev parent reply other threads:[~2011-01-31 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 19:41 [Qemu-devel] [PATCH] mingw32: Fix definitions for PRId64, PRIx64, PRIu64, PRIo64 Stefan Weil
2011-01-30 21:27 ` [Qemu-devel] " Stefan Weil
2011-01-30 21:39 ` Blue Swirl
2011-01-30 21:50 ` Stefan Weil
2011-01-30 22:14 ` Blue Swirl
2011-01-31 10:39 ` Mark Cave-Ayland [this message]
2011-01-31 17:25 ` Stefan Weil
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=4D469179.9080705@siriusit.co.uk \
--to=mark.cave-ayland@siriusit.co.uk \
--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).