Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Richard.Earnshaw@arm.com, simark@simark.ca, tom@tromey.com,
	tdevries@suse.de, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/python] Use PyConfig for python 3.9
Date: Thu, 13 Nov 2025 07:45:39 +0200	[thread overview]
Message-ID: <86ikfescxo.fsf@gnu.org> (raw)
In-Reply-To: <86h5uzt5pg.fsf@aarsen.me> (message from Arsen =?utf-8?Q?Arse?= =?utf-8?Q?novi=C4=87?= on Wed, 12 Nov 2025 20:24:11 +0100)

> From: Arsen Arsenović <arsen@aarsen.me>
> Cc: Richard.Earnshaw@arm.com,  simark@simark.ca,  tom@tromey.com,
>   tdevries@suse.de,  gdb-patches@sourceware.org
> Date: Wed, 12 Nov 2025 20:24:11 +0100
> 
> Are you aware of any users of Windows XP?

I was such a user until a year and a half ago, when the metal has died
of old age (it worked for 12 years, day in and day out) and I needed
to move on.  I still have that same XP system in a VM on my new
machine, although it now serves mainly for testing.

> Do you know why they still use it?

Until a year and a half ago, I was using it because the system was
rock-solid and stable, and since regular updates ceased a long time
ago, I could have the system up and running (and Emacs running on it)
for months on end without rebooting.

> Do you know if they do software updates, and whether their
> machines are networked (and, if so, please advise them to airgap or
> update them)?

Of course, it was connected to the Internet!  How do you think I could
do all the reviews of GDB documentation patches if it didn't?

> Also, other development tools already don't work on XP, Python being a
> good example from this very thread.

Python 3.4.4 still works.  As does mingw.org's MinGW, which has GCC
and Binutils.  To say nothing about Emacs.  Last significant GNU
packages I built natively on Windows XP (with 32-bit MinGW) before the
XP machine died were Binutils v2.41, GDB 14.1 (with Python and Guile),
Texinfo 7.1, Gawk 5.3.0, Make 4.4.1 and Emacs 28.2.  (They are all
available from my ezwinports site, btw.)

  reply	other threads:[~2025-11-13  5:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 13:36 Tom de Vries
2025-10-17 14:13 ` Tom Tromey
2025-10-17 15:11   ` Eli Zaretskii
2025-10-17 16:33     ` Tom Tromey
2025-10-17 18:34       ` Eli Zaretskii
2025-10-31 18:15         ` Tom Tromey
2025-11-01  7:00           ` Eli Zaretskii
2025-11-03 17:09             ` Simon Marchi
2025-11-03 18:21               ` Eli Zaretskii
2025-11-12 16:52                 ` Richard Earnshaw (foss)
2025-11-12 17:23                   ` Eli Zaretskii
2025-11-12 17:53                     ` Richard Earnshaw (foss)
2025-11-12 18:03                     ` Arsen Arsenović
2025-11-12 18:20                       ` Eli Zaretskii
2025-11-12 19:24                         ` Arsen Arsenović
2025-11-13  5:45                           ` Eli Zaretskii [this message]
2025-10-17 16:51     ` Arsen Arsenović
2025-10-17 18:35       ` 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=86ikfescxo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Richard.Earnshaw@arm.com \
    --cc=arsen@aarsen.me \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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