From c65ab984161ef321947cfdfefad8ea80242f338a Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Fri, 2 Mar 2007 21:30:00 +0000 Subject: [PATCH] * doc/gnulib-tool.texi (Initial import): Reword description of _FILE_OFFSET_BITS and _GNU_SOURCE, since they sometimes have a limited effect even if defined after the first system include. --- ChangeLog | 6 ++++++ doc/gnulib-tool.texi | 7 +++---- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index 4267fb65e..28ea90c22 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2007-03-02 Paul Eggert + + * doc/gnulib-tool.texi (Initial import): Reword description of + _FILE_OFFSET_BITS and _GNU_SOURCE, since they sometimes have a + limited effect even if defined after the first system include. + 2007-03-01 Bruno Haible * build-aux/config.libpath: Update to libtool-1.5.22. diff --git a/doc/gnulib-tool.texi b/doc/gnulib-tool.texi index a7f6ca7fe..db3e223da 100644 --- a/doc/gnulib-tool.texi +++ b/doc/gnulib-tool.texi @@ -235,10 +235,9 @@ 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. -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. +Also, on some platforms macros like @samp{_FILE_OFFSET_BITS} and +@samp{_GNU_SOURCE} may be ineffective, or may have only a limited +effect, if defined after 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 -- 2.11.0