From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, ktietz@redhat.com,
brobecker@adacore.com, fercerpav@gmail.com
Subject: Re: [PATCH] Add IPv6 support for remote TCP connections
Date: Sun, 22 Mar 2015 17:48:00 -0000 [thread overview]
Message-ID: <83iodssz5g.fsf@gnu.org> (raw)
In-Reply-To: <20150322170932.GA32091@host1.jankratochvil.net>
> Date: Sun, 22 Mar 2015 18:09:32 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, ktietz@redhat.com, brobecker@adacore.com,
> fercerpav@gmail.com
>
> On Sun, 22 Mar 2015 17:53:52 +0100, Eli Zaretskii wrote:
> > Not sure what this is about, but just FYI: getaddrinfo is available
> > only since Windows XP, so earlier versions will not have it. MinGW64
> > doesn't care about versions older than XP, so it's a small wonder it
> > compiles without a hitch.
>
> Even MS-Windows XP is EOLed already, isn't it?
Don't EOL me ;-) One of my machines (the one I'm typing this on,
actually) still happily runs XP, and probably will for some time to
come.
> What older MS-Windows release
> should be supported? I guess MS-Windows 2000? Do you mean it seriously?
It's up to us to decide. Emacs, for example, still supports Windows
98, per an explicit request from RMS, based on the large number of
users of those systems in the 3rd World.
> The patch of my attempt for gnulib import of getaddrinfo had 1.5MB and it was
> not easy due to conflict with all the existing MS-Windows #ifs in GDB code, is
> it really worth those EOLed OSes?
>
> I am really asking, the gnulib import does not seem right to me. This is also
> why the IPv6 support has been waiting for removal of the old OSes (like HP-UX).
Why can't we test at run time if getaddrinfo is available, and use it
if it is, else use the old code? This will work on Windows, and is
much simpler than the gnulib rigmarole.
next prev parent reply other threads:[~2015-03-22 17:48 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:54 Paul Fertser
2014-02-09 8:31 ` Jan Kratochvil
2014-02-09 9:53 ` Paul Fertser
2014-02-09 13:05 ` Jan Kratochvil
2014-02-09 16:35 ` Eli Zaretskii
2014-02-09 16:47 ` Jan Kratochvil
2014-02-09 17:08 ` Paul Fertser
2014-02-09 17:29 ` Jan Kratochvil
[not found] ` <1392033768-16793-1-git-send-email-fercerpav@gmail.com>
2014-02-10 16:53 ` [PATCH v2] " Eli Zaretskii
2014-02-10 17:02 ` Paul Fertser
2014-02-10 17:45 ` Eli Zaretskii
2014-02-10 19:58 ` getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections] Jan Kratochvil
2014-02-11 3:42 ` Joel Brobecker
2014-02-11 20:05 ` Jan Kratochvil
2014-02-11 20:33 ` Stan Shebs
2014-02-12 3:04 ` Joel Brobecker
2014-02-12 3:00 ` Joel Brobecker
2014-02-12 12:10 ` Jan Kratochvil
2014-02-13 7:37 ` Joel Brobecker
2014-02-13 10:44 ` [patch] [sim] --disable-sim on ppc* by default (for AIX) [Re: getaddrinfo available on all GDB hosts?] Jan Kratochvil
2014-02-13 10:51 ` Pedro Alves
2014-02-13 11:04 ` Jan Kratochvil
2014-02-13 11:39 ` Pedro Alves
2014-02-13 11:51 ` Joel Brobecker
2014-02-13 12:08 ` [cancel] " Jan Kratochvil
2014-02-13 11:59 ` Joel Brobecker
2014-02-13 14:26 ` getaddrinfo available on all GDB hosts? [Re: [PATCH v2] Add IPv6 support for remote TCP connections] Tom Tromey
2014-02-13 11:36 ` Jan Kratochvil
2014-02-13 11:55 ` Joel Brobecker
2014-02-11 19:48 ` [PATCH v3] Add IPv6 support for outgoing remote TCP connections Paul Fertser
2014-02-12 16:53 ` Jan Kratochvil
2014-02-12 17:32 ` Paul Fertser
2014-02-12 20:10 ` Jan Kratochvil
2015-03-22 16:39 ` [PATCH] Add IPv6 support for " Jan Kratochvil
2015-03-22 16:54 ` Eli Zaretskii
2015-03-22 17:09 ` Jan Kratochvil
2015-03-22 17:48 ` Eli Zaretskii [this message]
2015-03-23 18:02 ` Pedro Alves
2015-03-23 18:42 ` Eli Zaretskii
2015-03-23 19:12 ` Joel Brobecker
2015-03-23 19:18 ` Eli Zaretskii
2015-04-13 15:12 ` Pedro Alves
2015-04-13 15:27 ` Eli Zaretskii
2015-04-13 16:10 ` Pedro Alves
2015-03-23 19:19 ` Pedro Alves
2015-03-23 19:03 ` Corinna Vinschen
2015-03-23 19:12 ` Pedro Alves
2014-02-09 16:29 ` Eli Zaretskii
2014-02-09 16:25 ` 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=83iodssz5g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=fercerpav@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ktietz@redhat.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