On Fri, 2023-03-31 at 19:53 -0700, Paul Eggert wrote:
> On 2023-03-28 13:57, Richard Purdie wrote:
> > From a regression/failure point of view, the worrying issue is the
> > gpgme/mpg123 issue on x32 which also appears for musl 32 and 64 bit x86
> > targets.
> >
> > https://autobuilder.yoctoproje
Jacob Bachmeyer , Sat Apr 01 2023 04:54:22
GMT+0200 (Central European Summer Time)
A quick introduction to the situation for the Autoconf list:
The Automake maintainers have encountered a bizarre issue with
sporadic random test failures, seemingly due to "disk writes not
taking effect" (as Kar
A quick introduction to the situation for the Autoconf list:
The Automake maintainers have encountered a bizarre issue with sporadic
random test failures, seemingly due to "disk writes not taking effect"
(as Karl Berry mentioned when starting the thread). Bogdan appears to
have traced the iss
On 3/30/23 7:24 AM, Zack Weinberg wrote:
Please don't top-post on this mailing list.
On Tue, Mar 28, 2023, at 1:29 PM, Frederic Berat wrote:
On Tue, Mar 28, 2023 at 7:04 PM Nick Bowler wrote:
On 2023-03-28, Zack Weinberg wrote:
Can someone who understands the problem described at
https://li
Thanks for reporting that. I installed the attached slightly different
patch into Autoconf on Savannah. This patch also changes one other
instance of file timestamp comparison from < to <=. Something like this
should appear in the next Autoconf release.From 713d9822bbfb2923115065efaefed34a0113f8
On 2023-03-31 23:19, Khem Raj wrote:
I am also seeing this issue with packages using AC_EGREP_CPP
e.g. mcpp https://mcpp.sourceforge.net/download.html
when reconfigured it fails to run the resulting configure script
checking printf length modifier for the longest integer... (cached) ll
checki
