Re: [PATCH] Install new autoreconf files.

"Kevin J. McCarthy" <[email protected]>
Newsgroups gmane.mail.mutt.devel
Message-ID <ady-sgYzRnG2oV88@qinghai>
On Mon, Apr 13, 2026 at 08:01:28AM +0200, Rene Kita wrote:
>On Mon, Apr 13, 2026 at 12:44:21PM +0800, Kevin J. McCarthy wrote:
>> However, if anyone has more knowledge about this, I'd appreciate tips.
>
>Not sure if you saw it already, but a macOS user reported this on IRC
>some days ago. They were using GNU Autoconf 2.73.
>
>I used sr.ht CI to test if it is related to the autoconf version, but it
>looks like it is not that easy.
>
>I works with 2.73 on Alpine, but fails with 2.73 on Arch and FreeBSD.
>Works with 2.72 on OpenBSD.
>
>Grepping the web for this error did only bring this up:
>https://codeberg.org/ivarch/pv/issues/185

Ah, I missed it somehow.  I wonder why it triggered for them earlier, 
but for me not until now.

I'll push your patch up and see if my patch runs cleanly on sr.ht.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEiXWpszqjeRA4XFMIre92hIAxa9oFAmncvrIACgkQre92hIAx
a9ogWBAAg18g8sXoNY+8BjzGAXL0pe4GpKMXRHsboXtRXh6G89+wQ0zEplloViIo
ctvxHD1WPHQH4b1/CdiT9CXgGekO2xz8i17/hWWB2D9GKy0ygQbk08Yevazjg4it
NomSAqG4vJu7kKGgaYTJxsdgIlyasmUO/WeUqPYMt5SpQNeq7g5juxCnWcZKlBSx
YpoCIL3j+M3WElltornwYFwKqHLqRt+xrYHf5Ygf2Oa68ct3tssMVZ4z51VO+Kzf
BhkR/n99WM/ZHwzjgvgBoLJk+B1dVYyRuUHg1n03hQyaCBM3tKr+/zxdx0G3BgN9
TSNXsox9bfx9K928yc9ZWlEu4V8Z6hOAR1smB+plNOFtdQWCDg9nfKy+lSUzc5kZ
bE+fRx6qAYlN2pj7ZGls3Kq6hi38SDqlqP5xNE8826LNY7xM5aYpkD6zaZp5TJHB
tX6deaiJ5qjz+jycwtjSS2ENHWzmgsJXEHxyujlSEPKHON7I7cgxuOCVVXVRGMJ5
VPralMoLg1KZod/PNYrh12ZM+jMnJENPs73qCEpFq1hnpM1nadYpHlBwctAbZ/yT
wQ/Dx+hccAXevE+SCvahAbiLqtttOEwhUUi3BlzUB1FrEvs4Kbyto5fiHGMO0OKS
e2gPA/GGQXIne1zGloLZJbGjOOYyRdcCN5bPKCnEkBr8nux6FlY=
=QU+G
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.