Derek Robert Price wrote:
I understood that GNULIB had adopted freestanding C89 support as a
standard. As I understand it, wchar_t is specified to be in <stddef.h>
by C89, which is available to freestanding C89 compilers, so why is the
vasnprintf module checking for it at configure time?
If I remember it correctly, it's because of some Unices from ca. 1990-1994.
They have <stddef.h>, and when used with GCC, they support ANSI C. But
some of them don't have any wide-character facilities. I think SunOS 4
is one of them. Maybe also some more recent but virtually unmaintained
commercial BSDs.