Hi Maarten,
On 2020-11-23 16:06, Maarten L. Hekkelman wrote:
> These applications depend on libcifpp which is not yet processed so I
> could not use gbp to build packages, but that should not really be a
> problem.
I tried building cif-tools in a clean chroot, and ran into this:
dpkg-buildpackage
-----------------
Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package cif-tools
dpkg-buildpackage: info: source version 1.0.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Maarten L. Hekkelman
<maarten@hekkelman.com>
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
aclocal: warning: couldn't open directory 'config/m4': No such file or
directory
configure.ac:59: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:14: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
autoreconf seems to be unable to regenerate configure. Can you
investigate this issue?
Best,
Andrius