Mercurial > hg > octave-kai > gnulib-hg
changeset 11165:485c7346774b
Update comment about IBM C 9.0/10.1 bug.
author | Albert Chin-A-Young <china@thewrittenword.com> |
---|---|
date | Mon, 16 Feb 2009 00:02:34 +0100 |
parents | 90715da41753 |
children | 66432f187008 |
files | ChangeLog m4/include_next.m4 |
diffstat | 2 files changed, 15 insertions(+), 10 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2009-02-15 Albert Chin-A-Young <china@thewrittenword.com> + + * m4/include_next.m4: Update comment about IBM C 9.0/10.1 bug, now that + fixes are available from IBM. + 2009-02-13 Jim Meyering <meyering@redhat.com> fts: arrange not to stat non-directories in more cases
--- a/m4/include_next.m4 +++ b/m4/include_next.m4 @@ -1,5 +1,5 @@ -# include_next.m4 serial 10 -dnl Copyright (C) 2006-2008 Free Software Foundation, Inc. +# include_next.m4 serial 11 +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, dnl with or without modifications, as long as this notice is preserved. @@ -32,14 +32,14 @@ [gl_cv_have_include_next], [rm -rf conftestd1a conftestd1b conftestd2 mkdir conftestd1a conftestd1b conftestd2 - dnl The include of <stdio.h> is because IBM C 9.0 on AIX 6.1 supports - dnl include_next when used as first preprocessor directive in a file, - dnl but not when preceded by another include directive. Additionally, - dnl with this same compiler, include_next is a no-op when used in a - dnl header file that was included by specifying its absolute file name. - dnl Despite these two bugs, include_next is used in the compiler's - dnl <math.h>. By virtue of the second bug, we need to use include_next - dnl as well in this case. + dnl The include of <stdio.h> 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 <math.h>. By virtue of the + dnl second bug, we need to use include_next as well in this case. cat <<EOF > conftestd1a/conftest.h #define DEFINED_IN_CONFTESTD1 #include_next <conftest.h>