Paul Eggert wrote: > This includes ///opt/sun12/sunstudio12/prod/include/cc/time.h, which starts > off this way: > > #include_next <time.h> > > which resolves to "./time.h" so we are in a loop.
Thanks for explaining. This is effectively the same situation as with DEC cc (see <http://lists.gnu.org/archive/html/bug-gnulib/2007-04/msg00088.html>). In summary, if the compiler supports and uses include_next, gnulib's headers MUST use include_next as well. So your patch is perfect. Sorry for the questions. There are apparently more compilers that support #include_next: - Intel icc [1], - Portland Group pgCC -gnu_extensions [2], - Some C++ compiler from IBM [3]. Bruno [1] http://www.osc.edu/hpc/manuals/ia64/docs2/notes/ecc_fixes.txt [2] http://www.nacs.uci.edu/computing/gradea/docs/man/pgCC [3] http://www-304.ibm.com/jct03001c/software/awdtools/czos/features/czosv1r8.html
