[Pkg-electronics-devel] Bug#978820: ghdl: ftbfs with autoconf 2.70

[Matthias Klose]

Package: src:ghdl
Version: 0.37+dfsg-2
Severity: normal
Tags: sid bookworm
User: doko at debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/ghdl_0.37+dfsg-2_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
configure.ac:33: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
configure.ac:26: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:26: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
Running autoconf in src/libffi/...
configure.ac:19: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:19: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
Running autoconf in src/libgcc/...
Running autoconf in src/libgnatvsn/...
aclocal.m4:17: warning: this file was generated for autoconf 2.69.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically 'autoreconf'.
configure.ac:62: warning: The macro `AC_HEADER_STDC' is obsolete.
configure.ac:62: You should run autoupdate.
./lib/autoconf/headers.m4:657: AC_HEADER_STDC is expanded from...
configure.ac:62: the top level
aclocal.m4:17: warning: this file was generated for autoconf 2.69.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically 'autoreconf'.
configure.ac:16: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:16: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
configure.ac:4: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:4: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
Running autoconf in src/libgo/...
Running autoconf in src/libgomp/...
configure.ac:19: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:19: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
Running autoconf in src/libstdc++-v3/...
aclocal.m4:17: warning: this file was generated for autoconf 2.69.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically 'autoreconf'.
aclocal.m4:17: warning: this file was generated for autoconf 2.69.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically 'autoreconf'.
configure.ac:9: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:9: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
aclocal.m4:17: warning: this file was generated for autoconf 2.69.
You have another version of autoconf.  It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically 'autoreconf'.
configure.ac:4: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:4: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
configure.ac:3: error: Please use exactly Autoconf 2.69 instead of 2.69c.
../config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is expanded from...
configure.ac:3: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
make[2]: *** [debian/rules.patch:322: stamps/02-patch-stamp] Error 123
make[2]: Leaving directory '/<<PKGBUILDDIR>>/builddir/gcc'
make[1]: *** [debian/rules:70: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:48: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2