Re: btwowc(EOF) hang with gcc 4.4.2

[Bruno Haible]

Hi Eric,

> > @@ -34,6 +34,8 @@
> >      WCHAR_H=wchar.h
> >    fi
> > 
> > +  gl_WCHAR_H_INLINE_OK
> 
> Why not AC_REQUIRE it here?

Ok, I can use AC_REQUIRE here.

> > +  if test $gl_cv_header_wchar_h_correct_inline = no; then
> > +    AC_MSG_ERROR([<wchar.h> cannot be used with this compiler ($CC 
> > $CFLAGS).
> 
> Must we error out, or can we use AC_DEFINE/AC_SUBST to make our <wchar.h> 
> substitute work around the problem by never calling #include_next?

I think we would lose too much glibc functionality in this case. Starting with
the precise definition of mbstate_t, up to the support for -mlong-double-64.

Additionally, glibc's <wchar.h> is so broken that many packages that don't use
gnulib won't compile either, with -std=gnu99. We do a favour to the user if
we tell him to fix his system.

Bruno