Reuben Thomas wrote:
> In general, I reiterate the principle I implied with my request that
> #include_next warnings be suppressed some time ago: gnulib (and source
> libraries in general) should not generate warnings.
As explained in [1]: We cannot guarantee no warning. If you find warnings
obtained with generally useful options, like -Wall, we listen to you. But
there are cases where the problem is not on gnulib's side. For example,
- when you ask for exotic warnings, or
- There was one version of GCC, which introduced the "comparison between
signed and unsigned" warning, and it had no way of turning off this warning
without also turning off other, useful, warnings. In later versions,
the GCC developers realized that this warning is less useful than they
thought.
Bruno
http://lists.gnu.org/archive/html/bug-gnulib/2007-07/msg00014.html
