On Mon, May 21, 2001 at 08:45:32PM +0200, Akim Demaille wrote:
: | + After cleaning up the autoupdate warnings, I got the following warning
: | from autoconf:
: |
: | configure.in:1: error: possibly undefined macro: dnl
:
: Be aware that this message is definitely the sign that something is
: going wrong. If I were you, I'd restore the dnl, and would look for
: it in `configure' itself. It means that somewhere you were relying on
: the broken quotation of 2.13, or maybe that it is 2.50, trying to fix
: these issues, that broke you source.
Since this error message always uses the line-number of the first macro
and not the failed macro, couldn't we change scheme to insert a line
like the following in `configure' for each top-level macro invocation
(hopefully easy to detect)?:
#line configure.ac:43
Then we can scan for the last line of that kind before the first occurence
of the macro name in `configure' and output that the problem is somewhere
below that point.
Lars J
