Possible regressions with trunk autoconf (vs 2.71)

2022-11-16 Thread Frederic Berat
Hello, In the past few months, I worked on a tool that massively rebuild packages that depend on a specific other package, in order to help spot problems as early as possible (on Fedora and RHEL so far). I used this tool to check whether a new version of autoconf could lead to build failures in o

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-16 Thread Frederic Berat
uild with the work around, and try to figure out the other errors. Fred. On Wed, Nov 16, 2022 at 8:41 AM Frederic Berat wrote: > Hello, > > In the past few months, I worked on a tool that massively rebuild packages > that depend on a specific other package, in order to help spot probl

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-16 Thread Frederic Berat
into the other failures one by one now. On Wed, Nov 16, 2022 at 10:06 AM Frederic Berat wrote: > Hello again, > > Some progress on this, it looks like, at least for libpng, there is at one > place where the "Port AC_LANG_CALL" seems to be the culprit. > Specifically, the

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-16 Thread Frederic Berat
On Wed, Nov 16, 2022 at 4:27 PM Sam James wrote: > > > > > On 16 Nov 2022, at 07:41, Frederic Berat wrote: > > > > Hello, > > > > In the past few months, I worked on a tool that massively rebuild packages > > that depend on a specific other package, i

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-16 Thread Frederic Berat
On Wed, Nov 16, 2022 at 5:05 PM Arsen Arsenović wrote: > > > Frederic Berat writes: > > > Some progress on this, it looks like, at least for libpng, there is at one > > place where the "Port AC_LANG_CALL" seems to be the culprit. > > Specifically, the &q

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-17 Thread Frederic Berat
*/ #ifndef __i386__ yes #endif @@ -21873,11 +21869,15 @@ else case e in #( e) ac_cv_cpp_def___i386__=no ;; esac fi rm -rf conftest* -) + ;; +esac +fi +{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: $ac_cv_cpp_def___i386__" >&5 +printf "%s\n" &

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-17 Thread Frederic Berat
Yes and yes. On Thu, Nov 17, 2022 at 7:16 PM Paul Eggert wrote: > On 2022-11-17 04:41, Frederic Berat wrote: > > They have the following code in their aclocal.m4{,.cross} files: > > Does the attached, self-contained configure.ac illustrate the problem > for you? I don't

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-17 Thread Frederic Berat
Thanks, I'll update the bug I opened for them. On Thu, Nov 17, 2022 at 6:54 PM Zack Weinberg wrote: > On 2022-11-17 9:30 AM, Zack Weinberg wrote: > > Or even better, get rid of the AC_EGREP_CPP at the same time > > > > AC_CACHE_CHECK([whether we need to define $1], ac_var, > > [AC_PREPRO

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-18 Thread Frederic Berat
_PROG_EGREP], [AC_REQUIRE([AC_PROG_GREP])dnl +AC_REQUIRE([_AC_PROG_EGREP_TRADITIONAL])dnl AC_CACHE_CHECK([for egrep], ac_cv_path_EGREP, [if echo a | $GREP -E '(a|b)' >/dev/null 2>&1 then ac_cv_path_EGREP="$GREP -E" On Thu, Nov 17, 2022 at 7:16 PM Paul Eggert wrote:

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-18 Thread Frederic Berat
There are about 70 softwares (in Fedora ecosystem at least) which are affected by this comma. It will be hard for one person to track the upstream for each of them individually. I'll probably create issues at the package level on our side, so that their respective maintainers track the issue with

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-18 Thread Frederic Berat
d=2143724 [5] anjuta: https://bugzilla.redhat.com/show_bug.cgi?id=2143718 On Fri, Nov 18, 2022 at 6:30 PM Sam James wrote: > > > > > On 18 Nov 2022, at 07:11, Frederic Berat wrote: > > > > Thanks, I'll update the bug I opened for them. > > Could you share the links? Thanks.

Re: Possible regressions with trunk autoconf (vs 2.71)

2022-11-24 Thread Frederic Berat
srmio, ruby and apr. On top of that at least one package is affected by https://lists.gnu.org/archive/html/autoconf/2022-11/msg00110.html: cifs-utils The others are either quotation issues, or misplaced 'fi'. On Sat, Nov 19, 2022 at 8:21 AM Frederic Berat wrote: > > For now I track

Re: new snapshot available: autoconf-2.72c

2023-03-28 Thread Frederic Berat
Hello, This one is rather unfortunate. I've seen a similar problem on multiple packages, including make 4.4 (though not 4.4.1, so at least we can "simply" update). For now I also noticed rcs (5.10.1), gzip (1.12), ImageMagick (1:7.1.1.4) with similar failures. About 50% of the Fedora packages tha

Re: new snapshot available: autoconf-2.72c

2023-03-28 Thread Frederic Berat
Hello, Regarding EGREP, although I agree in principle this can be solved by using AS_CASE, I'd argue that the component actually required AC_PROG_EGREP. In principle, that should be enough, and requesting the user to know that internally there may be some need for "_AC_PROG_EGREP_TRADITIONAL" that

Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements

2023-03-28 Thread Frederic Berat
That's close enough, yes. You actually don't need the "else" though, it's enough to isolate the first call to egrep: % cat >configure.ac <<'EOF' AC_INIT([test], [0]) AC_PROG_CPP AC_PROG_EGREP # uncomment to make this work on new autoconf # m4_ifdef([_AC_PROG_EGREP_TRADITIONAL], [_AC_

Re: new snapshot available: autoconf-2.72c

2023-03-29 Thread Frederic Berat
Hi, I'm done walking through the Fedora rebuilds, I get the following failures due to largefile.m4 which breaks with autoconf: ImageMagick 1:7.1.1.4 emacs 1:28.2 grub2 2.06 gzip 1.12 libidn 1.41 libloc 0.9.16 make 4.4 parted 3.5 pspp 1.6.2 rcs 5.10.1 Indirectly: 'fatresize' (1.1.0) has a bug in

Re: autoconf 2.72/2.73 on RCS

2023-04-05 Thread Frederic Berat
On Mon, Apr 3, 2023 at 9:39 PM Zack Weinberg wrote: > > On Mon, Apr 3, 2023, at 12:25 PM, Paul Eggert wrote: > > On 2023-04-03 01:00, Frederic Berat wrote: > >> It would have been nice to keep these macro around for backward > >> compatibility. Assuming they are only

Re: [platform-testers] autoconf-2.72d released [beta]

2023-12-04 Thread Frederic Berat
On Mon, Dec 4, 2023 at 12:29 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Thu, 2023-11-30 at 16:51 -0500, Zack Weinberg wrote: > > We are pleased to announce beta release 2.72d of Autoconf. (Versions > > 2.72a, 2.72b, and 2.72c were development snapshots, not official alpha

Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?

2023-12-13 Thread Frederic Berat
On Wed, Dec 13, 2023 at 3:30 PM Florian Weimer wrote: > * Zack Weinberg: > > > Paul Eggert made some changes back in May that attempt to address this: > > commits 028526149ee804617a302ccef22cc6adbda681b0 and > > 33c26d2700f927432c756ccf7a4fc89403d35b95. Do you have a minimized > > test case for

Re: [platform-testers] autoconf-2.72e released [release candidate]

2023-12-20 Thread Frederic Berat
On Wed, Dec 20, 2023 at 5:17 PM Zack Weinberg wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > autoconf-2.72e is now available. This is a *release candidate* > for autoconf 2.72 final. Please test it as thoroughly as possible. > Testing in Windows- and Darwin-based environments wo

Re: [platform-testers] autoconf-2.72e released [release candidate]

2023-12-21 Thread Frederic Berat
On Wed, Dec 20, 2023 at 10:22 PM Zack Weinberg wrote: > On Wed, Dec 20, 2023, at 2:03 PM, Frederic Berat wrote: > > I admit I usually don't build the package for i386 since autoconf isn't > > arch dependent, but I did it this time and there are few test failures: >

Re: automake-1.17.90 pretest released [alpha]

2025-03-27 Thread Frederic Berat via Discussion list for the autoconf build system
On Wed, Feb 26, 2025 at 12:53 AM Karl Berry wrote: > This is to announce automake-1.17.90, a alpha release. > See the NEWS below for a brief summary of changes. > > Download here: > https://alpha.gnu.org/gnu/automake/automake-1.17.90.tar.gz > https://alpha.gnu.org/gnu/automake/automake-1.17.9