Re: [Mingw-users] mingw compiler bug?

[Bob R. <bob...@co...>]

On Fri, Dec 15, 2006 at 06:51:53AM +1300, Danny Smith wrote:
> 
>  Keith MARSHALL
>  Friday, 15 December 2006 4:23 a.m.
> > 
> > > - iconv support.  Not in MSVCRT, but should be okay with standalone
> > > libiconv.  However, I could not get the libstdc++ checks to pick up
> > > -liconv because the checks are braindead ...
> > 
> > So, some GCC autoconfigury hacking needed, to get this working.
> 
> Already works in GCC 4.x
> > 
> > > - langinfo.h, nl_langinfo().  Not in MSVCRT, not in libiconv.
> > > Even if the above stuff was fixed this would still not exist, unless
> > > someone has written wrappers for this API against the native Windows
> > > NLS stuff.
> > 
> Not needed foe wchar_t support in 4.x.  Something like nl_langifo needed
> for locale support.
> Better option would be to interface directly with w32api, which IMO has
> cleanner locale model than POSIX anyway. 
> 
> > FWIW, I've got a *very* rudimentary implementation, (just enough to
> > let `nl_langinfo( CODESET )' return the active codepage).  Probably
> > isn't enough for wchar_t support in libstdc++ would require, but if
> > anyone would like to help me develop it further, please contact me
> > off list.
> > 
> > > So it seems that wchar_t support in libstdc++ is only enabled if all
> > > of the above is present, which it is not.  So no wchar_t until then.
> 
> Get it now with 4.x.
> 
> Danny

Hi Danny,

I'm sort of a mingw noob. Are you saying that if I simply compile GCC
4.x, then this will all magically work?

Is there anything special that is done to compile GCC for mingw, or is
it simply like doing in on Linux? Does mingw keep patches to GCC?

Thanks,
Bob Rossi