On Tue, Aug 29, 2023 at 8:50 AM YunQiang Su via Binutils <binut...@sourceware.org> 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 fine. (To build GCC 5, I have noticed that --disable-libsanitizer is needed.)
