From: Tsutomu Seki <sekiriki@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] supports IPv6 only remote target
Date: Wed, 10 Feb 2016 18:55:00 -0000 [thread overview]
Message-ID: <CALZjo7vo2Mxd_pP4u192RgU989jEwn+D5sJVCTFiFRZsxpMp0Q@mail.gmail.com> (raw)
In-Reply-To: <83oaboa0x5.fsf@gnu.org>
Hi Eli,
> Is it feasible to copy the necessary bits from that header
I do not think so, because wspapi.h itself exists for backward compatibility.
It should be easier adding wspapi.h to MSYS than copying from it.
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) */
Is it better to try to update configure.ac to decide to use IPv6(getaddrinfo)
or stay on IPv4(gethostbyname)? I'm not familiar with autoconf, though.
# I'm resending this message because I'd accidentally sent HTML mail
# from smartphone and it was rejected. I'm sorry if you have received
# duplicated message.
Regards,
Seki, Tsutomu
2016-02-11 3:13 GMT+09:00 Eli Zaretskii <eliz@gnu.org>:
>> Date: Wed, 10 Feb 2016 20:43:40 +0900
>> From: Tsutomu Seki <sekiriki@gmail.com>
>> Cc: gdb-patches@sourceware.org
>>
>> Changed address to be "@code{fe80::1%eth1}", to include scope id
>> as written later.
>>
>> > This example seems to imply that more than just taking brackets
>> > is required.
>>
>> Your are right. This implies address/port separation rule and
>> address/scope separation rule. The former should be documented,
>> because address/port separation is done by the application before
>> passing them to getaddrinfo.
>>
>> > Should we tell more about that?
>>
>> On the other hand, the latter is difficult to document (for me) in
>> generic manner, because %-style scope-id notation depends on
>> implementation of getaddrinfo.
>
> I think what you did is good enough, thanks.
>
>> > I think this will break the build with mingw.org's MinGW. It doesn't
>> > have wspiapi.h, AFAIK. What exactly is needed from that header?
>>
>> It is needed to support getaddrinfo() on Windows 2000 and older versions.
>>
>> What can I do for it? The easiest solution is to replace with <ws2tcpip.h>,
>> but Windows 2000 support (as a host) would be dropped.
>
> Is it feasible to copy the necessary bits from that header, i.e. have
> the prototype in ser-tcp.c (or in some suitable GDB header file)?
>
> Thanks.
next prev parent reply other threads:[~2016-02-10 18:55 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 [this message]
2016-02-10 19:22 ` Eli Zaretskii
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=CALZjo7vo2Mxd_pP4u192RgU989jEwn+D5sJVCTFiFRZsxpMp0Q@mail.gmail.com \
--to=sekiriki@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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).