>>>>> "Erez" == Erez Zadok <[EMAIL PROTECTED]> writes:
>> configure.in:35: warning: The macro `AC_OUTPUT_COMMANDS' is
>> obsolete. You should run autoupdate. configure.in: 33:
>> `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
>> configure.in:50: warning: The macro `AC_LANG_C' is obsolete.
>> configure.in:29: warning: AC_C_CONST was called before
>> AC_PROG_CC_STDC
Erez> I've asked about it a while back, and was told that these were
Erez> new changes in autoconf/automake and that you wanted to wait
Erez> until autconf became more stable. It's been a while since those
Erez> changes were put in, no? Shouldn't libool try to keep up w/
Erez> autoconf? I think it has to, b/c once the new autoconf is
Erez> released, you'd pretty much have to update libtool so the
Erez> warnings go away (else you'll get many similar user complaints).
The picture is no longer to have the three amigos released together.
In particular, neither next Automake nor next Libtool will use newer
names.
It took quite a while until people, especially Alexandre, managed to
convince me that those warnings are frightening people, so there will
be an option in autoconf to enable those warnings.
AC_LANG_C and so on are broken, so from the point of view of Autoconf
we have to move to AC_LANG(C). There are plenty of other macros which
changed or are obsoleted. But it is probably too soon to have
Automake and Libtool depend upon it.
Nevertheless, once next Autoconf and next Libtool are released,
Autoconf will be, and shortly afterwards there should be a release of
Automake and Libtool using the newer Autoconf.
Akim
