Bruno Haible clisp.org> writes:
>
> Albert Chin wrote:
> > The patch below would work around this and disable #include_next on this
> > platform.
> >
> > --
> > albert chin (china thewrittenword.com)
> >
> > -- snip snip
> > diff --git a/m4/include_next.m4 b/m4/include_next.m4
> > index 08c6
Albert Chin wrote:
> The patch below would work around this and disable #include_next on this
> platform.
>
> --
> albert chin ([EMAIL PROTECTED])
>
> -- snip snip
> diff --git a/m4/include_next.m4 b/m4/include_next.m4
> index 08c63db..f0f947b 100644
> --- a/m4/include_next.m4
> +++ b/m4/include
On Thu, Sep 04, 2008 at 12:26:43PM -0500, Albert Chin wrote:
> [[ snip snip ]]
>
> Compiler bug? It seems like #include_next isn't working. Oddly, if I
> modify fcntl.h so it's just:
> #include_next
> then everything works. But, if I precede the #include_next with other
> #include directives, t
lib/clean-temp.c has:
...
#include
#include
and lib/fcntl.in.h has:
#ifndef _GL_FCNTL_H
@PRAGMA_SYSTEM_HEADER@
#include
#include
#include
/* The include_next requires a split double-inclusion guard. */
[EMAIL PROTECTED]@ @NEXT_FCNTL_H@
On AIX 5.3:
$ cd /tmp/z
$ cat
