From: Ulrich Drepper <drepper@redhat.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: [RFC] database with API information
Date: Fri, 9 Sep 2022 19:07:33 +0200 [thread overview]
Message-ID: <CAP3s5k9UdWfgChPhRah1rQ2M13ZocbCOA-vdN4M6GdbTV=Jm3A@mail.gmail.com> (raw)
In-Reply-To: <6CBFC8BD-97C0-46EA-9D7F-6AD72146B9E8@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Fri, Sep 9, 2022 at 5:26 PM Iain Sandoe <idsandoe@googlemail.com> wrote:
> One small request, I realise that Python 2 is dead, but I regularly
> bootstrap GCC
> on older machines that only have Python 2 installations. If possible (and
> it sounds
> plausible if the job is really quite simple) - it would be good to support
> those older
> machines without having to take a detour to find a way to build Python 3
> on them first.
>
Would this really be an issue? Just as is the case for the gperf-generated
files, the repository would contain the generated files and gperf/python
would only be needed if someone changes those files or explicitly removes
them.
next prev parent reply other threads:[~2022-09-09 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 6:22 Ulrich Drepper
2022-09-07 10:56 ` Richard Sandiford
2022-09-07 12:33 ` Martin Liška
2022-09-09 15:26 ` Iain Sandoe
2022-09-09 17:07 ` Ulrich Drepper [this message]
2022-09-09 17:13 ` Iain Sandoe
2022-09-09 11:40 ` SAIFI
2022-09-09 11:47 ` Jonathan Wakely
2022-09-09 12:29 ` SAIFI
2022-09-09 15:06 ` Jonathan Wakely
2022-09-09 16:41 ` SAIFI
2022-09-09 18:21 ` Jonathan Wakely
2022-09-09 18:40 ` SAIFI
2022-09-09 20:05 ` Jonathan Wakely
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='CAP3s5k9UdWfgChPhRah1rQ2M13ZocbCOA-vdN4M6GdbTV=Jm3A@mail.gmail.com' \
--to=drepper@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=idsandoe@googlemail.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).