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 are fairly common. Many of them are not valid C code at all, and GCC increasingly detects that (for example, “warning: conflicting types for built-in function”).
Florian _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
