Re: autoconf broken when forcing -Werror -pedantic
From:
Lawrence Velázquez
Subject:
Re: autoconf broken when forcing -Werror -pedantic
Date:
Sun, 06 Jul 2025 23:40:00 -0400
On Sun, Jul 6, 2025, at 10:25 PM, Martin D Kealey wrote:
> To help me find bugs in a range of projects, I have a wrapper around gcc
> that forces -Werror -pedantic.
>
> [...]
>
> A significant source of detection failures is that the probes assume that
> K&R function declarations (without parameters) are still valid. (Bzzzt!
> Nope.)
>
> [...]
>
> *autoconf --version*
>> autoconf (GNU Autoconf) 2.71
>> Copyright (C) 2021 Free Software Foundation, Inc.
These threads might be of interest. Some of the issues you're
describing may have been addressed in Autoconf 2.72.
https://lists.gnu.org/archive/html/autoconf/2022-11/msg00000.htmlhttps://lists.gnu.org/archive/html/autoconf/2023-12/msg00005.html
> I expect to get a lot of errors during builds - that's the point - but what
> I didn't expect was for autoconf to be broken.
At least one person thinks that it doesn't make sense to run configure
scripts this way in the first place.
https://lists.gnu.org/archive/html/autoconf/2023-12/msg00008.html
> Are there any plans to improve autoconf?
This question seems more appropriate for <autoconf@gnu.org>.
--
vq