This is the mail archive of the
mailing list for the glibc project.
Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
- From: Zack Weinberg <zackw at panix dot com>
- To: Paul Eggert <eggert at cs dot ucla dot edu>
- Cc: Nick Bowler <nbowler at draconx dot ca>, autoconf at gnu dot org, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 1 Sep 2016 21:58:10 -0400
- Subject: Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
- Authentication-results: sourceware.org; auth=none
- References: <CAKCAbMgx-N-w4iuCh3+GkMOup=FQ749vd_qPJ2qyZusaVsnEgQ@mail.gmail.com> <CADyTPEzsvKjY+wPOE7V=1jOpzDW+npojohsEbk2C42oDLyeWSg@mail.gmail.com> <CAKCAbMiU62_7RrNFaVsRzBd93DE+Kuj+XF3KLw3ChF4LedwZ_A@mail.gmail.com> <firstname.lastname@example.org>
On Thu, Sep 1, 2016 at 9:32 PM, Paul Eggert <email@example.com> wrote:
>>> It seems that the simplest short term solution is to just not use
>>> -Werror when building packages. Other than the warning, the header
>>> detection worked, and the test is behaving as documented, right?
>> AC_HEADER_MAJOR is obeying the letter of its documentation but not the
>> spirit. People using it reasonably expect that it should handle this
>> transition seamlessly for them.
> Sure, but Nick's correct that Autoconf-generated code typically cannot be
> configured with -Werror, as there are too many false positives. The problem
> with AC_HEADER_MAJOR is just one of many. So I wouldn't worry about a change
> causing an error for that case. People should not configure with -Werror,
> that's all.
The original problem was that AC_HEADER_MAJOR doesn't detect that
glibc 2.25 is throwing warnings, so a *build* with -Werror fails. I
agree that telling people to *configure* with -Werror is a