Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autoreconf will fail when calling autoheader on Linux system #26

Open
hosiet opened this issue Feb 14, 2018 · 9 comments
Open

Autoreconf will fail when calling autoheader on Linux system #26

hosiet opened this issue Feb 14, 2018 · 9 comments

Comments

@hosiet
Copy link

hosiet commented Feb 14, 2018

% 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?

@bmc
Copy link
Owner

bmc commented Feb 14, 2018

Not off the top of my head. Might be an autoconf version mismatch. I'll have to look into it.

@hosiet
Copy link
Author

hosiet commented Feb 14, 2018

Just FYI, I am using the latest Autotools toolchain as provided by Debian unstable.

@bmc
Copy link
Owner

bmc commented Feb 16, 2018

Yeah, pretty sure that's not the (version of the) toolchain I used when I originally developed this thing.

@hosiet
Copy link
Author

hosiet commented Feb 16, 2018

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!

@bmc
Copy link
Owner

bmc commented Feb 16, 2018

I'll get to it when I can. I have a day job. :-)

@hosiet
Copy link
Author

hosiet commented May 23, 2018

Hi @bmc , is there any updates for this issue?

2 similar comments
@hosiet
Copy link
Author

hosiet commented Jul 26, 2018

Hi @bmc , is there any updates for this issue?

@hosiet
Copy link
Author

hosiet commented Nov 20, 2018

Hi @bmc , is there any updates for this issue?

@bmc
Copy link
Owner

bmc commented Nov 26, 2018

Note that there's a workaround to this issue:

make distclean
rm -rf autom4te.cache configure
autoconf
make

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants