From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Daniel Jacobowitz <dan@codesourcery.com>,
ktietz70@googlemail.com, Ozkan Sezer <sezeroz@gmail.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] winsock include fixes
Date: Sun, 28 Mar 2010 19:01:00 -0000 [thread overview]
Message-ID: <20100328190133.GA32263@ednor.casa.cgf.cx> (raw)
In-Reply-To: <647fe9b11003281148u489bb801oabb0c7bd6d4438e7@mail.gmail.com>
On Sun, Mar 28, 2010 at 09:48:04PM +0300, Ozkan Sezer wrote:
>On Sun, Mar 28, 2010 at 9:43 PM, Christopher Faylor wrote:
>> On Fri, Mar 26, 2010 at 11:33:02AM -0400, Daniel Jacobowitz wrote:
>>>On Fri, Mar 26, 2010 at 05:24:23PM +0200, Ozkan Sezer wrote:
>>>> Indeed, adding winsock2.h include to serial.h does fix the
>>>> problems for mingw-w64, like the following:
>>>
>>>This change is OK.
>>
>> Isn't this really a problem with mingw-w64 rather than a gdb
>> problem? ?It seems like this should be fixed there.
>
>I posted the fix to gdb, because I believe that it is a gdb problem.
>Can you explain how is it really supposed to be a mingw-w64 problem?
Actually, nevermind. I've just googled this and it seems like including
winsock2.h first is the accepted solution even for regular Visual C.
cgf
prev parent reply other threads:[~2010-03-28 19:01 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
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 [this message]
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=20100328190133.GA32263@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ktietz70@googlemail.com \
--cc=sezeroz@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