This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Don't recommend specific GCC version in installation documentation
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Fri, 28 Jun 2013 23:04:20 +0000
- Subject: Re: Don't recommend specific GCC version in installation documentation
- References: <Pine dot LNX dot 4 dot 64 dot 1306282216410 dot 15167 at digraph dot polyomino dot org dot uk> <20130628223522 dot 38C812C09C at topped-with-meat dot com>
On Fri, 28 Jun 2013, Roland McGrath wrote:
> I think the general recommendation to try the latest stable GCC is fine.
> But rather than saying just that, we need to say something like, "At the
> time of this release, GCC versions up to @testedgcc{} are known to work.
> If newer GCC versions have trouble building a working library and there is
> no newer release of @theglibc{} you can use instead, then you may need to
> an older GCC version to build @theglibc{}."
I don't like actually naming a specific tested version here; it adds yet
another thing to update for each release. It seems better to establish a
policy that glibc releases need to work with the most recent major GCC
release as of when the first glibc release from that series was released,
and then document that principle rather than specific versions (so 4.8 was
most recent major release as of glibc 2.18, so all glibc 2.18.x releases
should work with GCC 4.8.y and using the most recent 4.8.y is generally
appropriate). Something like "Releases of @theglibc{} are tested to build
using the stable GCC release series current when the first @glibcadj{}
release (@var{major}.@var{minor}) of a series
(@var{major}.@var{minor}.@var{patchlevel}) is released.".
--
Joseph S. Myers
joseph@codesourcery.com