Gnulib doesn't impose ordering constraints between include files, except

for <config.h>.

1 files changed, 4 insertions, 4 deletions

diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi
index cb37964a54..a7f6ca7feb 100644
--- a/doc/gnulib-tool.texi
+++ b/doc/gnulib-tool.texi
@@ -235,10 +235,10 @@ file.  That way, for example, if @file{config.h} defines
 @samp{restrict} to be the empty string on a pre-C99 host, or a macro
 like @samp{_FILE_OFFSET_BITS} that affects the layout of data
 structures, the definition is consistent for all include files.
-
-You should include Gnulib-provided headers before system headers,
-so that Gnulib-provided headers can adjust how a system header
-behaves.
+Another reason why @file{config.h} must be included before any other
+include file is that it may define macros like @samp{_GNU_SOURCE}
+or @samp{_FILE_OFFSET_BITS} which, on glibc systems, have an effect only
+if defined before the first system header file is included.
 
 A final word of warning: Gnulib currently assumes it will be
 responsible for @emph{all} functions that end up in the Autoconf