From: Bruno Haible Date: Tue, 17 Feb 2009 22:43:29 +0000 (+0100) Subject: Reformulate comment. X-Git-Tag: v0.1~6316 X-Git-Url: http://erislabs.org.uk/gitweb/?a=commitdiff_plain;h=2f23fbb2ce253697930e8f769e13134f9be81363;p=gnulib.git Reformulate comment. --- diff --git a/ChangeLog b/ChangeLog index 97d6fb61a..4146057ab 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2009-02-17 James Youngman + Bruno Haible + + * m4/include_next.m4: Reformulate comment. + 2009-02-16 Jim Meyering fts: add #if guards so that the fts_lgpl module still builds diff --git a/m4/include_next.m4 b/m4/include_next.m4 index 752263901..d6101fe32 100644 --- a/m4/include_next.m4 +++ b/m4/include_next.m4 @@ -1,4 +1,4 @@ -# include_next.m4 serial 11 +# include_next.m4 serial 12 dnl Copyright (C) 2006-2009 Free Software Foundation, Inc. dnl This file is free software; the Free Software Foundation dnl gives unlimited permission to copy and/or distribute it, @@ -32,14 +32,15 @@ AC_DEFUN([gl_INCLUDE_NEXT], [gl_cv_have_include_next], [rm -rf conftestd1a conftestd1b conftestd2 mkdir conftestd1a conftestd1b conftestd2 - dnl The include of is because IBM C 9.0, 10.1 (original - dnl versions, prior to 2009-01 updates) on AIX 6.1 supports include_next - dnl when used as first preprocessor directive in a file, but not when - dnl preceded by another include directive. Additionally, with this same - dnl compiler, include_next is a no-op when used in a header file that was - dnl included by specifying its absolute file name. Despite these two bugs, - dnl include_next is used in the compiler's . By virtue of the - dnl second bug, we need to use include_next as well in this case. + dnl IBM C 9.0, 10.1 (original versions, prior to the 2009-01 updates) on + dnl AIX 6.1 support include_next when used as first preprocessor directive + dnl in a file, but not when preceded by another include directive. Check + dnl for this bug by including . + dnl Additionally, with this same compiler, include_next is a no-op when + dnl used in a header file that was included by specifying its absolute + dnl file name. Despite these two bugs, include_next is used in the + dnl compiler's . By virtue of the second bug, we need to use + dnl include_next as well in this case. cat < conftestd1a/conftest.h #define DEFINED_IN_CONFTESTD1 #include_next