Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ozkan Sezer <sezeroz@gmail.com>
To: dan@codesourcery.com
Cc: gdb-patches@sources.redhat.com, ktietz70@googlemail.com
Subject: Re: [PATCH] winsock include fixes
Date: Fri, 26 Mar 2010 15:24:00 -0000	[thread overview]
Message-ID: <647fe9b11003260824o4fb82825n22ca8cdf5da0f1e6@mail.gmail.com> (raw)
In-Reply-To: <647fe9b11003260747i3156003fp642e9ed6ae74d7b5@mail.gmail.com>

On Fri, Mar 26, 2010 at 4:47 PM, Ozkan Sezer <sezeroz@gmail.com> wrote:
> On Fri, Mar 26, 2010 at 4:17 PM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
>> On Fri, Mar 26, 2010 at 12:54:10PM +0200, Ozkan Sezer wrote:
>>> Hi: Here is a patch fixing the winsock include problem
>>> which appeared after the recent winsock header work in
>>> mingw-w64-headers.
>>
>> This patch isn't OK, because it fixes an inclusion order problem by
>> moving things around without a comment.  Everywhere else the
>> "gdb_XXX.h" headers are included in a group, last.  So someone's going
>> to clean up these files and reintroduce the problem.
>>
>> It sounds like part of the problem is the inclusion of winsock2.h in
>> gdb_select.h, and windows.h in serial.h.  Should we include both
>> headers in both files to avoid the problem?
>>
>> --
>> Daniel Jacobowitz
>> CodeSourcery
>>
>
> That may be a solution, too: Inclusion of winsock2.h
> should be harmless in all cases when USE_WIN32API
> is defined.
>
> --
> Ozkan
>

Indeed, adding winsock2.h include to serial.h does fix the
problems for mingw-w64, like the following:

Index: gdb/serial.h
===================================================================
RCS file: /cvs/src/src/gdb/serial.h,v
retrieving revision 1.21
diff -u -p -r1.21 serial.h
--- gdb/serial.h	1 Jan 2010 07:31:41 -0000	1.21
+++ gdb/serial.h	26 Mar 2010 15:21:45 -0000
@@ -21,6 +21,7 @@
 #define SERIAL_H

 #ifdef USE_WIN32API
+#include <winsock2.h>
 #include <windows.h>
 #endif

Compile tested for x86_64-w64-mingw32 and i686-w64-mingw32.

--
Ozkan


  reply	other threads:[~2010-03-26 15:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 10:54 Ozkan Sezer
2010-03-26 11:15 ` Kai Tietz
2010-03-26 11:20   ` Kai Tietz
2010-03-26 11:21   ` Ozkan Sezer
2010-03-26 14:17 ` Daniel Jacobowitz
2010-03-26 14:47   ` Ozkan Sezer
2010-03-26 15:24     ` Ozkan Sezer [this message]
2010-03-26 15:33       ` Daniel Jacobowitz
2010-03-26 15:35         ` Ozkan Sezer
2010-03-27 16:15         ` Ozkan Sezer
2010-03-30 18:08           ` Tom Tromey
2010-03-30 18:18             ` Ozkan Sezer
2010-03-28 18:43         ` Christopher Faylor
2010-03-28 18:48           ` Ozkan Sezer
2010-03-28 19:01             ` Christopher Faylor

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=647fe9b11003260824o4fb82825n22ca8cdf5da0f1e6@mail.gmail.com \
    --to=sezeroz@gmail.com \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ktietz70@googlemail.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