Hello, Akim!
I'm sorry if I did someting wrong. Everything that I removed didn't look
like legitimate automake messages.
I was debugging another bug and I discovered that I don't understand the
messages produced by "autoreconf --force --verbose", i.e. it was hard to
figure out what program produced what output.
> Automake. Actually you should also have removed the
>
> warn 'automake: Autoconf traces is an experimental feature';
> warn 'automake: use at your own risks';
Nope. "automake: " makes them legitimate.
I'm restoring the "traces:" lines. Sorry.
Regards,
Pavel Roskin
________________________________
--- ChangeLog
+++ ChangeLog
@@ -1,5 +1,7 @@
2001-02-02 Pavel Roskin <[EMAIL PROTECTED]>
+ * automake.in (scan_autoconf_traces): Restore trace messages.
+
* automake.in (handle_aclocal_m4): Fix stripping of the initial
"./" from the dependencies of aclocal.m4.
Reported by Ralf Corsepius.
--- automake.in
+++ automake.in
@@ -4375,6 +4375,7 @@
# _AC_LIBOBJ_DECL and use it the in various macros.
if (!defined $libsources{$source})
{
+ print STDERR "traces: discovered $source\n";
$libsources{$source} = $here;
}
}
@@ -4382,6 +4383,7 @@
{
if (!defined $configure_vars{$args[0]})
{
+ print STDERR "traces: discovered AC_SUBST($args[0])\n";
$configure_vars{$args[0]} = $here;
}
}
________________________________
