Re: autoconf 2.72/2.73

On Sat, Apr 1, 2023 at 4:27=E2=80=AFAM Paul Eggert <[email protected]> wro=
te:
>
> On 2023-03-31 00:46, Christoph Karl wrote:
> > Due to a future release of autoconf
> > there will be the following problem with rcs:
>
> If you're building from an RCS release tarball you should be OK, as that
> build shouldn't use Autoconf.
>
> If you're building a modified version of RCS, or building from Git,
> you'll need bleeding-edge Gnulib if you also use a bleeding-edge
> Autoconf. Something like the attached compressed build log, say. I just
> now did that on Ubuntu 22.10 and it worked for me. I was using Autoconf
> 2.72c.5-18744 (i.e., built from Autoconf commit
> 05e295b60cfdf378b7ed8c1f8563a5644d5d4689 dated Fri Mar 31 10:55:29 2023
> -0700).

The build is done from an RCS tarball, but auroconf/autoreconf is
called. Which leads to failure:

+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/rcs-5.10.1.tar.lz
+ STATUS=3D0
+ '[' 0 -ne 0 ']'
+ cd rcs-5.10.1
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ autoconf
aclocal.m4:17: warning: this file was generated for autoconf 2.71.
You have another version of autoconf.  It may work, but is not guaranteed t=
o.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically 'autorecon=
f'.
configure:8208: error: possibly undefined macro: _AC_SYS_LARGEFILE_TEST_INC=
LUDES
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
error: Bad exit status from /var/tmp/rpm-tmp.1o6acq (%prep)

Fred.