Re: AT_MTIME_DELAY not working? (was: Re: [platform-testers] autoconf-2.72e released [release candidate])

2023-12-22 Thread Zack Weinberg
On Thu, Dec 21, 2023, at 10:07 PM, Jacob Bachmeyer wrote: > Zack Weinberg wrote: >> On Thu, Dec 21, 2023, at 3:27 AM, Frederic Berat wrote: >>> 11: autoconf: forbidden tokens, basic FAILED (tools.at:481) >>> So far I got it on aarch64 and s390x. Timing issue maybe ? >> >> Yeah, this

AT_MTIME_DELAY not working? (was: Re: [platform-testers] autoconf-2.72e released [release candidate])

2023-12-21 Thread Jacob Bachmeyer
Zack Weinberg wrote: On Thu, Dec 21, 2023, at 3:27 AM, Frederic Berat wrote: On Wed, Dec 20, 2023 at 10:22 PM Zack Weinberg wrote: I also get this one that fails once in a while (3 failures out of 12 executions): 11: autoconf: forbidden tokens, basic FAILED (tools.at:481) So

Re: autoconf-2.72e released [release candidate]

2023-12-21 Thread Zack Weinberg
On Wed, Dec 20, 2023, at 7:41 PM, Alan Coopersmith wrote: > On 12/20/23 08:16, Zack Weinberg wrote: >> 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 would be

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

2023-12-21 Thread Zack Weinberg
On Thu, Dec 21, 2023, at 3:27 AM, Frederic Berat wrote: > On Wed, Dec 20, 2023 at 10:22 PM Zack Weinberg wrote: > I also get this one that fails once in a while (3 failures out of 12 > executions): > > 11: autoconf: forbidden tokens, basic FAILED (tools.at:481) > > So far I got it o

Re: autoconf-2.72e released [release candidate]

2023-12-21 Thread Alan Coopersmith
On 12/20/23 08:16, Zack Weinberg wrote: 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 would be particularly helpful. Testing your own project’s configure.ac wit

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: > > > > 420: AC_SYS_LARGEFILE

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

2023-12-20 Thread Zack Weinberg
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: > > 420: AC_SYS_LARGEFILEFAILED (semantics.at:908) > 421: AC_SY

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

autoconf-2.72e released [release candidate]

2023-12-20 Thread Zack Weinberg
-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 would be particularly helpful. Testing your own project’s configu