From: Eli Zaretskii <eliz@gnu.org>
To: Tsutomu Seki <sekiriki@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] supports IPv6 only remote target
Date: Wed, 10 Feb 2016 19:22:00 -0000 [thread overview]
Message-ID: <83h9hg9xrj.fsf@gnu.org> (raw)
In-Reply-To: <CALZjo7vo2Mxd_pP4u192RgU989jEwn+D5sJVCTFiFRZsxpMp0Q@mail.gmail.com> (message from Tsutomu Seki on Thu, 11 Feb 2016 03:55:29 +0900)
> Date: Thu, 11 Feb 2016 03:55:29 +0900
> From: Tsutomu Seki <sekiriki@gmail.com>
> Cc: gdb-patches@sourceware.org
>
> MSYS ws2tcpip.h says;
>
> #if (_WIN32_WINNT >= _WIN32_WINNT_WINXP)
> /**
> * For WIN2K the user includes wspiapi.h for these functions.
> */
> void WSAAPI freeaddrinfo (struct addrinfo*);
> int WSAAPI getaddrinfo (const char*,const char*,const struct addrinfo*,
> struct addrinfo**);
> int WSAAPI getnameinfo(const struct sockaddr*,socklen_t,char*,DWORD,
> char*,DWORD,int);
> #endif /* (_WIN32_WINNT >= _WIN32_WINNT_WINXP) */
Yes, because AFAIK you can have getaddrinfo on W2K only if you install
an optional upgrade kit.
> Is it better to try to update configure.ac to decide to use IPv6(getaddrinfo)
> or stay on IPv4(gethostbyname)?
No, not on Windows, where a binary compiled on one system can then be
run on another.
Do we care about W2K support at this point? AFAIK, quite a few
MinGW64 headers require and set _WIN32_WINNT to a value that will
exclude W2K anyway.
I suggest to wait for Pedro or Joel to chime in on this issue.
Thanks.
next prev parent reply other threads:[~2016-02-10 19:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 13:50 Tsutomu Seki
2016-02-09 17:29 ` Eli Zaretskii
2016-02-10 11:43 ` Tsutomu Seki
2016-02-10 18:14 ` Eli Zaretskii
2016-02-10 18:55 ` Tsutomu Seki
2016-02-10 19:22 ` Eli Zaretskii [this message]
2016-03-10 16:44 ` Pedro Alves
2016-03-10 21:20 ` Paul Fertser
2016-03-11 1:42 ` Tsutomu Seki
2016-03-11 10:25 ` Pedro Alves
2018-04-10 19:21 ` Sergio Durigan Junior
2018-04-10 20:05 ` Paul Fertser
2018-04-11 2:26 ` Eli Zaretskii
2018-04-11 12:19 ` Tsutomu Seki
2018-04-11 16:18 ` Sergio Durigan Junior
2016-03-11 15:52 ` Eli Zaretskii
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=83h9hg9xrj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sekiriki@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 read-only IMAP folder(s) and NNTP newsgroup(s).