Follow-up Comment #12, sr #110397 (project autoconf):
First off, yes, automake should change its test to read something like
AC_INIT([smoketest], [1])
AC_OUTPUT
(Calling `AC_INIT` with no arguments is also deprecated.)
However, something else is wrong as well -- I have a bad feeling that this may
affect any diagnostic emitted by autoconf. What happens if you run autoconf
2.70 on _this_ test file?
AC_INIT([test], [1])
AC_USG
AC_OUTPUT
You ought to get output more or less like this:
conftest.ac:2: warning: The macro `AC_USG' is obsolete.
conftest.ac:2: You should run autoupdate.
../lib/autoconf/headers.m4:822: AC_USG is expanded from...
conftest.ac:2: the top level
It would also be interesting to know what this command prints:
m4 --nesting-limit=1024 --gnu --include=$PREFIX/share/autoconf \
--debug=aflq --fatal-warning --trace=_m4_warn \
--reload-state=$PREFIX/share/autoconf/autoconf.m4f \
$PREFIX/share/autoconf/trailer.m4 conftest.ac > /dev/null
where $PREFIX is the installation prefix. It _ought_ to print something like
this:
m4trace:conftest.ac:2: -1- _m4_warn([obsolete], [The macro `AC_USG' is
obsolete.
You should run autoupdate.], [../lib/autoconf/headers.m4:822: AC_USG is
expanded from...
conftest.ac:2: the top level])
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110397>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
