This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)

From: Florian Weimer <fweimer at redhat dot com>
To: Nick Bowler <nbowler at draconx dot ca>, Zack Weinberg <zackw at panix dot com>
Cc: autoconf at gnu dot org, GNU C Library <libc-alpha at sourceware dot org>
Date: Thu, 1 Sep 2016 07:51:06 +0200
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>

On 09/01/2016 06:37 AM, Nick Bowler 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?

-Werror does not work because warnings from autoconf test snippets arefairly common. Many of them are not valid C code at all, and GCCincreasingly detects that (for example, “warning: conflicting types forbuilt-in function”).


Florian

References:
- AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  - From: Zack Weinberg
- Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  - From: Nick Bowler

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]