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 <fcntl.h>
> then everything works. But, if I precede the #include_next with other
> #include directives, the error above occurs. Definitely seems like a
> compiler bug. The #include directive seems to be resetting the order of
> the search paths.
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_next.m4
@@ -30,6 +30,7 @@ AC_DEFUN([gl_INCLUDE_NEXT],
mkdir conftestd1 conftestd2
cat <<EOF > conftestd1/conftest.h
#define DEFINED_IN_CONFTESTD1
+#include <stdio.h>
#include_next <conftest.h>
#ifdef DEFINED_IN_CONFTESTD2
int foo;
