From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] w32: Undefine error constants before their redefinition
Date: Thu, 29 Mar 2012 20:36:37 +0200 [thread overview]
Message-ID: <4F74ABB5.5070708@siemens.com> (raw)
In-Reply-To: <4F74A3B8.5040805@mail.berlios.de>
On 2012-03-29 20:02, Stefan Weil wrote:
> Am 28.03.2012 20:56, schrieb Jan Kiszka:
>> Avoids lots of warnings.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> qemu_socket.h | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/qemu_socket.h b/qemu_socket.h
>> index fe4cf6c..51ad210 100644
>> --- a/qemu_socket.h
>> +++ b/qemu_socket.h
>> @@ -8,7 +8,9 @@
>> #include <ws2tcpip.h>
>>
>> #define socket_error() WSAGetLastError()
>> +#undef EWOULDBLOCK
>> #undef EINTR
>> +#undef EINPROGRESS
>> #define EWOULDBLOCK WSAEWOULDBLOCK
>> #define EINTR WSAEINTR
>> #define EINPROGRESS WSAEINPROGRESS
>
> Hi,
>
> I am curious: with which version of MinGW or Cygwin do you get warnings?
> I don't see them in my native and cross MinGW / MinGW-w64 builds.
Not sure if that is what you are looking for, but my runtime rpm claims
to be mingw32-runtime-20120126-1.4.
>
> Where do the original definitions come from, and are they compatible with
> the redefined values? If yes, it might be possible to put the new
> definitions
> in a conditionally compiled code block (#if !defined(EWOULDBLOCK) ...
> #endif).
/usr/i686-w64-mingw32/sys-root/mingw/include/errno.h:158:0: note: this
is the location of the previous definition
And there we have e.g.
#ifndef EINPROGRESS
#define EINPROGRESS 112
#endif
vs.
#define WSAEINPROGRESS 10036L
>
> Could slirp/slirp.h also use qemu_socket.h? That would simplify the code.
> Is it possible to move those definitions to qemu-os-win32.h? I'd prefer
> to have them in some w32 specific header file instead of qemu_socket.h and
> slirp/slirp.h.
/me too. But as I cannot test w32, I would welcome to receive a tested
patch for the slirp queue. :)
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] w32: Undefine error constants before their redefinition
Date: Thu, 29 Mar 2012 20:36:37 +0200 [thread overview]
Message-ID: <4F74ABB5.5070708@siemens.com> (raw)
In-Reply-To: <4F74A3B8.5040805@mail.berlios.de>
On 2012-03-29 20:02, Stefan Weil wrote:
> Am 28.03.2012 20:56, schrieb Jan Kiszka:
>> Avoids lots of warnings.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> qemu_socket.h | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/qemu_socket.h b/qemu_socket.h
>> index fe4cf6c..51ad210 100644
>> --- a/qemu_socket.h
>> +++ b/qemu_socket.h
>> @@ -8,7 +8,9 @@
>> #include <ws2tcpip.h>
>>
>> #define socket_error() WSAGetLastError()
>> +#undef EWOULDBLOCK
>> #undef EINTR
>> +#undef EINPROGRESS
>> #define EWOULDBLOCK WSAEWOULDBLOCK
>> #define EINTR WSAEINTR
>> #define EINPROGRESS WSAEINPROGRESS
>
> Hi,
>
> I am curious: with which version of MinGW or Cygwin do you get warnings?
> I don't see them in my native and cross MinGW / MinGW-w64 builds.
Not sure if that is what you are looking for, but my runtime rpm claims
to be mingw32-runtime-20120126-1.4.
>
> Where do the original definitions come from, and are they compatible with
> the redefined values? If yes, it might be possible to put the new
> definitions
> in a conditionally compiled code block (#if !defined(EWOULDBLOCK) ...
> #endif).
/usr/i686-w64-mingw32/sys-root/mingw/include/errno.h:158:0: note: this
is the location of the previous definition
And there we have e.g.
#ifndef EINPROGRESS
#define EINPROGRESS 112
#endif
vs.
#define WSAEINPROGRESS 10036L
>
> Could slirp/slirp.h also use qemu_socket.h? That would simplify the code.
> Is it possible to move those definitions to qemu-os-win32.h? I'd prefer
> to have them in some w32 specific header file instead of qemu_socket.h and
> slirp/slirp.h.
/me too. But as I cannot test w32, I would welcome to receive a tested
patch for the slirp queue. :)
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-03-29 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 18:56 [Qemu-trivial] [PATCH] w32: Undefine error constants before their redefinition Jan Kiszka
2012-03-28 18:56 ` [Qemu-devel] " Jan Kiszka
2012-03-29 6:53 ` [Qemu-trivial] " Stefan Hajnoczi
2012-03-29 6:53 ` [Qemu-devel] " Stefan Hajnoczi
2012-03-29 18:02 ` [Qemu-trivial] [Qemu-devel] " Stefan Weil
2012-03-29 18:02 ` Stefan Weil
2012-03-29 18:36 ` Jan Kiszka [this message]
2012-03-29 18:36 ` Jan Kiszka
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=4F74ABB5.5070708@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=weil@mail.berlios.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.