Re: Failure crossing gcc 3.3.3 from GNU/Linux to MinGW

[llewelly at xmission dot com]

"Stephan T. Lavavej" <stl@caltech.edu> writes:

> Thanks for the reply.
> 
> [Gabriel Dos Reis]
> > As you probably know, in the nutshell, native builds on MinGW
> > or Cygwin do not have support for wchar_t so corresponding
> > support in libstdc++ is disabled.  It looks like when
> > building the cross, you did -not- take that fact into
> > consideration and somehow requested support for wchar_t while
> > the underlying C functions are missing.
> 
> But how did I do that?  In my build script, I configure cross binutils,
> cross gcc, and crossed-native gcc with --disable-nls.
> 
> Or does that not affect wchar gunk at all?
> 
> How can I disable the wchar stuff explicitly?

I think you want to add --disable-c-mbchar  to your configure line for
gcc. 
See http://gcc.gnu.org/onlinedocs/libstdc++/configopts.html
However I don't have a cygwin system to test this on.

There are two caveats to this flag: (a) it makes a libstdc++ without
wchar support and therefor farther from the ISO standard, and (b) C++
built with a --disable-c-mbchar configured compiler may not be
linkable with code built with a --enable-c-mbchar compiler.