public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/26607] GDB build failure in gnulib if building on Windows version older than 8
Date: Sat, 12 Sep 2020 15:23:53 +0000 [thread overview]
Message-ID: <bug-26607-4717-ybiTKvud6b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26607-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26607
--- Comment #2 from Joel Brobecker <brobecker at gnat dot com> ---
For reference, the following page at Microsoft web page, current as of Aug
2020,
says the following:
- Windows 7 end of mainstream support: Jan 2015
- Windows 7 end of extended support: Jan 2020
... and ...
- Windows 8.1 end of mainstream support: Jan 2018
- Windows 8.1 end of extended support: Jan 2023
For Vista, the following page confirms Vista (extended?) supported was ended:
Apr 2017
Members of the gnulib community might find it hard to spend energy on this
issue, and this may also affect the GDB community's stance on the minimum
requirement in terms of Windows version to build it.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-12 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 15:11 [Bug build/26607] New: " brobecker at gnat dot com
2020-09-12 15:12 ` [Bug build/26607] " brobecker at gnat dot com
2020-09-12 15:13 ` brobecker at gnat dot com
2020-09-12 15:23 ` brobecker at gnat dot com [this message]
2020-09-14 11:04 ` cbiesinger at google dot com
2020-10-09 19:51 ` cvs-commit at gcc dot gnu.org
2020-10-09 20:41 ` brobecker at gnat dot com
2022-12-02 15:42 ` tromey at sourceware dot org
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=bug-26607-4717-ybiTKvud6b@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).