>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Mar 13, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> And again, I shall emphasize that this little comfort is a myth:
>> you *need* to update Automake if you update Autoconf, let it be
>> because Automake still doesn't support AC_CONFIG_FILES,
>> AC_CONFIG_HEADERS and the like, new AC_SUBST variables etc.
Alexandre> But I'm not talking about updating autoconf, that's the
Alexandre> whole point. I just wanted to update automake, and,
Alexandre> because of a minor patch that fixed one minor inconvenience
Alexandre> (an autoconf warning), I wasted a whole hour investigating
Alexandre> a problem that seemed to be totally unrelated.
I agree, but as I said, I'm really hoping that we will soon move the
--trace, so it is just trying to sneak in before the door is really
closed.
Alexandre> Whenever automake decides it's time to adopt the new
Alexandre> autoconf's features, I won't be able to update automake
Alexandre> without updating autoconf too. Before that, I'd rather not
Alexandre> fall into this trap again.
I hope we start this this week or the next, but we should not wait
longer.
>> I don't understand what you mean. This issue has be commented
>> several times, and in addition the guilty message is given
>> explicitly in the warning.
Alexandre> I was using autoconf 2.13, and automake's missing.m4
Alexandre> contained:
Alexandre> AC_MSG_WARN([`missing'...])
Alexandre> Note, the backtick was not quoted. The quote had been
Alexandre> removed to silence CVS autoconf.
Aaah, didn't understand, sorry. Yep, this kind of trap is painful.
zsh -x does a good job here. And I really thought that Automake had
not changed its missing.m4.
Automake should AC_PREREQ(2.14a).
Alexandre> he'll get weird error messages from [s]hell! :-)
:) :)
