Re: Using gnulib with -pedantic, I get many warnings about #include_next

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Reuben Thomas on 8/24/2008 4:47 PM:
>> gnulib cannot avoid the use of #include_next. On non-glibc platforms it
>> would be possible, by use of #include <absolute_system_header_filename>,
>> but with glibc it is not possible, because glibc itself uses
>> #include_next.

But obviously, glibc has some way of marking a header file as a system
header, so that the use of extensions such as #include_next do not trigger
gcc -pedantic warnings.  Is there a #pragma that glibc uses to do that?
And should gnulib do the same?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkix5kkACgkQ84KuGfSFAYCk1wCfafL9xdTCdD7MvrEoK8ilucEG
7PQAn1vCZP9+qkZQ/BYQj2F1ZGtQBfHf
=aFjp
-----END PGP SIGNATURE-----