qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 2/3] w64: Add definition of FMT_pid
Date: Fri, 15 Jul 2011 21:38:13 +0200	[thread overview]
Message-ID: <1310758694-6360-3-git-send-email-weil@mail.berlios.de> (raw)
In-Reply-To: <1310758694-6360-1-git-send-email-weil@mail.berlios.de>

For mingw-w64, pid_t is _pid_t which is __int64,
so this platform needs its own definition of FMT_pid.

Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
 osdep.h |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/osdep.h b/osdep.h
index a817017..252d050 100644
--- a/osdep.h
+++ b/osdep.h
@@ -130,6 +130,8 @@ int qemu_madvise(void *addr, size_t len, int advice);
 
 #if defined(__HAIKU__) && defined(__i386__)
 #define FMT_pid "%ld"
+#elif defined(WIN64)
+#define FMT_pid "%" PRId64
 #else
 #define FMT_pid "%d"
 #endif
-- 
1.7.2.5

  parent reply	other threads:[~2011-07-15 19:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 19:38 [Qemu-devel] New patches for w32, w64 Stefan Weil
2011-07-15 19:38 ` [Qemu-devel] [PATCH 1/3] Fix conversions from pointer to tcg_target_long Stefan Weil
2011-07-18  3:19   ` Guan Xuetao
2011-07-18  7:39   ` Alexander Graf
2011-07-15 19:38 ` Stefan Weil [this message]
2011-07-15 20:39   ` [Qemu-devel] [PATCH 2/3] w64: Add definition of FMT_pid Andreas Färber
2011-07-15 19:38 ` [Qemu-devel] [PATCH 3/3] w32: Fix format string regression Stefan Weil
2011-07-15 20:42   ` Andreas Färber
2011-07-17  9:03     ` Blue Swirl
2011-07-17 18:34       ` Stefan Weil
2011-07-17 21:31         ` Blue Swirl
2011-08-13  9:38 ` [Qemu-devel] New patches for w32, w64 Stefan Weil
2011-08-13 10:49   ` Blue Swirl
2011-08-21 16:40 ` Blue Swirl

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=1310758694-6360-3-git-send-email-weil@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --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).