public inbox for
 help / color / mirror / Atom feed
From: Fangrui Song <>
To: YunQiang Su <>, Jakub Jelinek <>,
	Nick Clifton <>
Subject: Re: RFC: Top level configure: Require a minimum version 6.8 texinfo
Date: Tue, 29 Aug 2023 09:09:28 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Aug 29, 2023 at 8:50 AM YunQiang Su via Binutils
<> wrote:
> > 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.

I wonder whether documents can be disabled. When people build old
packages, they may not care about the documentation.

I tried to build gcc 4.4.7 yesterday with gcc 12 and failed due to a
tex syntax error.
I could not figure out why, and `configure MAKEINFO=true` did not
help, so I switched to `truncate -s0 gcc/doc/*`.

I just tried binutils and did not find a way to disable doc, either.
To me, if doc can be disabled, any makeinfo version requirement is
(To build GCC 5, I have noticed that --disable-libsanitizer is needed.)

  reply	other threads:[~2023-08-29 16:15 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
2023-08-29 16:09     ` Fangrui Song [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).