This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
makeinfo version required (was: define_constraints patch, re-revised)
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: gcc at gcc dot gnu dot org, Mark Mitchell <mark at codesourcery dot com>
- Cc: Ranjit Mathew <rmathew at gmail dot com>, Zack Weinberg <zackw at panix dot com>
- Date: Tue, 28 Feb 2006 22:02:03 +0100 (CET)
- Subject: makeinfo version required (was: define_constraints patch, re-revised)
- References: <20060227065229.GA18445@panix.com> <4403E086.8080101@gmail.com> <20060228061310.GA15647@panix.com> <Pine.BSF.4.62.0602281138140.65792@pulcherrima.dbai.tuwien.ac.at> <4404A743.7010502@codesourcery.com>
[ gcc-patches -> gcc ]
On Tue, 28 Feb 2006, Mark Mitchell wrote:
>> That said, I guess it's fine to ignore the ones with makeinfo 4.5,
>> but based on my checks I'd be rather hesitant for us to require
>> anything later than 4.6.
> I don't think we should tie our own hands in this way. Building GCC
> requires lots of tools; so be it. We could always have a check that
> avoids building the documentation for old makeinfo.
That would cause all sorts of problems for users of the BSD Ports
Collections, to just give an example.
That said, I don't really disagree about enforcing proper prerequisites to
build GCC and its documentation, my question in this case, and in general,
just is: Can the issue which we encountered be worked around in a simple
way in our .texi sources, or is it important enough to warrant ramping up
our requirements?
(I don't know which is the case here, I just feel we shouldn't ramp up
our requirements too readily.)
Gerald