Autoreconf will fail when calling autoheader on Linux system
% autoreconf --install --verbose --force
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal --force
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
autoreconf: configure.in: tracing
autoreconf: configure.in: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
autoheader: warning: missing template: HAVE_BASENAME
autoheader: Use AC_DEFINE([HAVE_BASENAME], [], [Description])
autoheader: warning: missing template: HAVE_FLOCK
autoheader: warning: missing template: HAVE_SETENV
autoreconf: /usr/bin/autoheader failed with exit status: 1
Is there any suggestions to fix this problem?
Not off the top of my head. Might be an autoconf version mismatch. I'll have to look into it.
Just FYI, I am using the latest Autotools toolchain as provided by Debian unstable.
Yeah, pretty sure that's not the (version of the) toolchain I used when I originally developed this thing.
Okay. So could you please dig a little bit more into it and make sure we could properly run autoreconf against contemporary Autotools toolchain?
Thanks!
I'll get to it when I can. I have a day job. :-)
Hi @bmc , is there any updates for this issue?
Hi @bmc , is there any updates for this issue?
Hi @bmc , is there any updates for this issue?
Note that there's a workaround to this issue:
make distclean
rm -rf autom4te.cache configure
autoconf
make