[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: possibly undefined macro: dnl
From: |
Stephen Torri |
Subject: |
Re: possibly undefined macro: dnl |
Date: |
Tue, 7 Aug 2001 14:39:52 -0400 (EDT) |
On 7 Aug 2001, Alexandre Duret-Lutz wrote:
> Too much quoting, I'd say.
>
> The last time I have seen this error I had mispelled
> AC_CACHE_CHECK([a], [b], [... dnl ...])
> into
> QC_CACHE_CHECK([a], [b], [... dnl ...])
> While the first case is evaluated by m4 as expected,
> the second is simply output as
> QC_CACHE_CHECK(a, b, ... dnl ...)
> hence the warning.
Here is the output of autoconf running:
configure.in:184: warning: AC_PROG_LEX invoked multiple times
configure.in:3: error: possibly undefined macro: dnl
configure.in:379: error: possibly undefined macro: AC_LIBTOOL_CXX
line 3 reads: dnl
line 379 reads: AC_LIBTOOL_CXX
Looking at these two and the surrounding area I cannot see a problem with
quoting or bad names.
Stephen
- possibly undefined macro: dnl, Stephen Torri, 2001/08/07
- Re: possibly undefined macro: dnl, Alexandre Duret-Lutz, 2001/08/07
- Re: possibly undefined macro: dnl,
Stephen Torri <=
- Re: possibly undefined macro: dnl, Alexandre Duret-Lutz, 2001/08/08
- Re: possibly undefined macro: dnl, Akim Demaille, 2001/08/09
- Re: possibly undefined macro: dnl, Alexandre Duret-Lutz, 2001/08/09
- Re: possibly undefined macro: dnl, Akim Demaille, 2001/08/09
- Re: possibly undefined macro: dnl, Alexandre Duret-Lutz, 2001/08/09