bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: manywarnings for C++


From: Reuben Thomas
Subject: Re: manywarnings for C++
Date: Mon, 7 Aug 2017 17:11:17 +0100

On 7 August 2017 at 16:42, Bruno Haible <address@hidden> wrote:

> Currently in my configure.ac, I have:
>
>   AC_LANG_PUSH([C++])
>   gl_MANYWARN_ALL_GCC([cxx_warnings])
>
>   dnl Enable all G++ warnings not in this list.
>   gl_MANYWARN_COMPLEMENT([cxx_warnings], [$cxx_warnings], [$nw])
>   for w in $cxx_warnings; do
>     gl_WARN_ADD([$w])
>   done
>   AC_LANG_POP
>
> which seems to work.

Yes, this is how the multi-language facilities are supposed to be used.

​OK, now that some of the code is in a new file, I get:

configure.ac:90: error: gl_MANYWARN_ALL_GCC: unknown language: C++
m4/manywarnings.m4:38: gl_MANYWARN_ALL_GCC is expanded from...
configure.ac:90: the top level

Line 90 is the call of gl_MANYWARN_ALL_GCC in the code extract above.​

The main reason why the AC_LANG_PUSH/POP pairs are still there is that the
macros can be AC_REQUIREd.

​Ah, I see, thanks.

--

reply via email to

[Prev in Thread] Current Thread [Next in Thread]