This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RFC: requiring GCC >= 4.7 to build glibc
- From: Florian Weimer <fweimer at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 5 Oct 2015 22:41:23 +0200
- Subject: Re: RFC: requiring GCC >= 4.7 to build glibc
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1508201344140 dot 30940 at digraph dot polyomino dot org dot uk> <5612CBD3 dot 9040601 at redhat dot com> <alpine dot DEB dot 2 dot 10 dot 1510052025330 dot 17637 at digraph dot polyomino dot org dot uk>
On 10/05/2015 10:34 PM, Joseph Myers wrote:
> Are you saying that binutils 2.22 support is in fact already broken (which
> is something I'd take as evidence to justify such a move - that people are
> actually using features in glibc that 2.22 doesn't have)?
Yes, binutils 2.22 is broken on x86_64, and I don't think 2.23 will fix
it. There are 2.23 versions versions with backported features which
work. But I think we currently require upstream binutils 2.24 at least,
maybe newer. We have a similar problem on s390x, with even tighter
requirements.
We just don't have a culture of adding proper configure checks for the
binutils features we use. We simply let it break. This means that
bumping the nominal requirement does not provide any cleanup
opportunities, and it also does not inconvenience downstreams (who will
just have to continue to patch around unsupported features).
Florian