qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Roy Tam <roytam@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] fix MinGW compilation when --enable-vnc-jpeg is specified
Date: Sat, 18 Jun 2011 10:35:57 +0200	[thread overview]
Message-ID: <4DFC636D.9090800@mail.berlios.de> (raw)
In-Reply-To: <BANLkTika6YmzRYAnta8TgQGpLSpoAdpKNQ@mail.gmail.com>

Am 18.06.2011 07:13, schrieb Roy Tam:
> This patch fix conflicting types for 'INT32' in basetsd.h in including
> qemu-common.h first.
>
>
> Sign-off-by: Roy Tam<roytam@gmail.com>
> --
> diff --git a/ui/vnc-enc-tight.c b/ui/vnc-enc-tight.c
> index 87fdf35..1591df0 100644
> --- a/ui/vnc-enc-tight.c
> +++ b/ui/vnc-enc-tight.c
> @@ -28,6 +28,8 @@
>
>   #include "config-host.h"
>
> +#include "qemu-common.h"
> +
>   #ifdef CONFIG_VNC_PNG
>   #include<png.h>
>   #endif
> @@ -36,8 +38,6 @@
>   #include<jpeglib.h>
>   #endif
>
> -#include "qemu-common.h"
> -
>   #include "bswap.h"
>   #include "qint.h"
>   #include "vnc.h"

Acked-by: Stefan Weil <weil@mail.berlios.de>

The conflicting declaration is in jmorecfg.h which is included from 
jpeglib.h.

  reply	other threads:[~2011-06-18  8:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18  5:13 [Qemu-devel] [PATCH] fix MinGW compilation when --enable-vnc-jpeg is specified Roy Tam
2011-06-18  8:35 ` Stefan Weil [this message]
2011-06-23 13:52   ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2011-06-23 15:05     ` Stefan Weil
2011-06-24  5:30       ` Stefan Hajnoczi
2011-06-26 18:06       ` Blue Swirl
2011-06-26 20:03         ` Stefan Weil
2011-06-26 20:26           ` Blue Swirl
2011-06-27  2:37             ` TeLeMan
2011-06-27  4:15               ` Roy Tam
2011-06-27  5:40               ` Stefan Weil
2011-06-27  5:56                 ` Roy Tam
2011-06-27 17:22                   ` Stefan Weil
2011-06-30 15:26                     ` Paolo Bonzini

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=4DFC636D.9090800@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=roytam@gmail.com \
    /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).