need to define _ISOC99_SOURCE
Bruno Haible
haible@ilog.fr
Fri Jul 28 07:39:00 GMT 2000
Akim Demaille writes:
> BTW, there is a macro I dislike even more, it's:
>
> - Macro: AC_PROG_GCC_TRADITIONAL
> Add `-traditional' to output variable `CC' if using the GNU C
> compiler and `ioctl' does not work properly without
> `-traditional'. That usually happens when the fixed header files
> have not been installed on an old system. Since recent versions
> of the GNU C compiler fix the header files automatically when
> installed, this is becoming a less prevalent problem.
>
> I'd like to have opinions on this one: should it be swallowed in an
> AC_CHECK_FUNC or so? Should it be systematically run? Should we
> deprecate this macro?
I'd deprecate it. It solved a problem with SunOS 4.0.x long ago. We
shouldn't make people think that -traditional is good for anything,
when in fact more and more sources cannot be compiled in K&R mode.
> | AC_DEFINE(_GNU_SOURCE, 1,
> | [Define unconditionally for setting a GNU environment.])
>
> C and C++ or just C?
Both. In C++ you get an error when you use an undeclared function, in
C normally only a warning.
Bruno
More information about the Libc-alpha
mailing list