From: YunQiang Su <wzssyqa@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Nick Clifton <nickc@redhat.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: RFC: Top level configure: Require a minimum version 6.8 texinfo
Date: Tue, 29 Aug 2023 23:50:20 +0800 [thread overview]
Message-ID: <CAKcpw6V33tWLd0tk16yWDUEP7PgqS5G-wym6tmRM9_xwaJz1_g@mail.gmail.com> (raw)
In-Reply-To: <ZO4SkOWbpCGbvT6T@tucnak>
> I think that is too new.
> We still allow building gcc e.g. with GCC 4.8 from ~ 10 years ago and
> I think various boxes where people regularly build gcc will have similarly
> old other tools.
> So, bumping requirement from ~ 20 years old tools to ~ 10 years old tools
> might be ok, but requiring ones at most 2 years old will be a nightmare,
I agree.
Lots of toolchains distributed by CPU vendors are supposed to support
CentOS 6, or at least 7.
next prev parent reply other threads:[~2023-08-29 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:21 Nick Clifton
2023-08-29 15:45 ` Jakub Jelinek
2023-08-29 15:50 ` YunQiang Su [this message]
2023-08-29 16:09 ` Fangrui Song
2023-08-29 16:01 ` Eli Zaretskii
2023-08-29 16:09 ` Xi Ruoyao
2023-08-29 17:07 ` Tom Tromey
2023-08-30 2:53 ` Eric Gallager
2023-08-30 20:28 ` Tom Tromey
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=CAKcpw6V33tWLd0tk16yWDUEP7PgqS5G-wym6tmRM9_xwaJz1_g@mail.gmail.com \
--to=wzssyqa@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jakub@redhat.com \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).