Re: different CFLAGS for gnulib code?

[Jim Meyering]

On Fri, Jan 15, 2021 at 12:55 AM Bruno Haible <bruno@clisp.org> wrote:
> Jeffrey Walton wrote:
> > Perhaps it would be a good idea to filter-out the options that you
> > don't want present for Gnulib.
...
> It is an interesting idea. Leaving the question aside how it is implemented
> (through an AC_SUBSTed variable or what else), the main question is: Would
> some GNU package maintainers want this?
>
> I always thought that GNU package maintainers want their entire package to
> be compiled with the same CFLAGS and CPPFLAGS. Would compiling the gnulib
> part with options for fewer warnings be OK with you?
>
> Paul, Pádraig, Jim, Paul, Akim, Simon, all: what's your opinion?

Yes, I do something like that in every package for which I make
releases, these days.
There is a separate clause in configure.ac where we arrange to remove
troublesome warning options from the global list to form the CFLAGS
options used for gnulib proper:
AC_SUBST([GNULIB_WARN_CFLAGS])

and sometimes also (e.g., in grep) where we do similar for gnulib tests:
  AC_SUBST([GNULIB_TEST_WARN_CFLAGS])