Bruno Haible via Gnulib discussion list <[email protected]> writes:

> +  # Gnulib uses #include_next in many .h files.
> +  AS_VAR_APPEND([$1], [' -Wno-gnu-include-next'])

Do clang really trigger on gnulib *.h's?  I would have expected to have
run into this.  Doesn't it just trigger for the *.c compilation module?

I would want to catch any use of '#include_next' in any of my non-gnulib
*.c files, so if it behaves like I think it does, the warning seem
useful to me.

/Simon

Attachment: signature.asc
Description: PGP signature

Reply via email to