[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problems with #include_next in gnulib's string_.h on DEC C compiler
From: |
James Youngman |
Subject: |
Problems with #include_next in gnulib's string_.h on DEC C compiler |
Date: |
Sat, 26 May 2007 12:31:24 +0100 |
I've had a bug report of compilation failure in some gnulib code from
someone using
DEC C V5.9-005 on Digital UNIX V4.0 (Rev. 1229) on OSF/1 4.0F.
I suspect that the basic problem is that gnulib's string.h uses
unclude_next but the compiler does not support it:
cc: Warning: ./stdlib.h, line 36: "include_next" is an invalid
preprocessor directive, and is being ignored. (baddirective)
# include_next <stdlib.h>
--^
cc: Warning: ./string.h, line 21: "include_next" is an invalid
preprocessor directive, and is being ignored. (baddirective)
# include_next <string.h>
--^
I think the code under consideration is this:-
#ifdef __DECC
# include_next <string.h>
#endif
The compiler goes on to produce fatal errors about use the undefined
type size_t, but I would assume these are a consequence of the
inability to include the system <string.h>, which I assume defines it.
I don't have access to the affected system, but Nelson Beebe (in the
CC: list) does.
James.
- Problems with #include_next in gnulib's string_.h on DEC C compiler,
James Youngman <=