[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Paul Eggert
Subject: Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
Date: Thu, 1 Sep 2016 18:32:32 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

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.

This has long been common practice among Autoconf users. For example:

There's your problem right there.  We really do not recommend the use of
CFLAGS=-Werror during configuration, because it simply does not work.
Seriously - the recommendation on this list is that you never use
-Werror during configure (except maybe to temporarily probe whether
-Werror even works);

reply via email to

[Prev in Thread] Current Thread [Next in Thread]