Reuben Thomas wrote: > it'd need some way for gnulib to turn it off, and > gnulib would then have to use it.
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. Bruno
