[Bug libstdc++/40802] Libstdc++ is broken for win32 host

xenofears at gmail dot com gcc-bugzilla@gcc.gnu.org
Mon Jul 20 20:52:00 GMT 2009



------- Comment #8 from xenofears at gmail dot com  2009-07-20 20:51 -------
Subject: Re:  Libstdc++ is broken for win32 host

Why are you going on? I told you, since you outspokenly don't care and/or 
have no plans of looking at it, your post as such is unnecessary, unless you 
are speaking for the entire gcc development team. I think you misread it. If 
you do (speak for the entire gcc development team), then please leave it for 
the few people who do care can deal with it.

And, by the way, it worked just fine, I svn updated gcc, and it stopped 
working. Nothing else changed. It is not the target, it is the *host*, look 
again. The build from same code for Linux x64 host works. Please do 
something constructive and fix the title, which should be win64 not win32 
(as you should be already aware of.)

--------------------------------------------------
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
Sent: Monday, July 20, 2009 4:25 PM
To: <xenofears@gmail.com>
Subject: [Bug libstdc++/40802] Libstdc++ is broken for win32 host

>
>
> ------- Comment #7 from paolo dot carlini at oracle dot com  2009-07-20 
> 20:25 -------
> Let's also add a mingw maintainer. In fact, I think this PR should be just
> recategorized as <target>, the generic libstdc++ code is very unlikely to 
> be at
> fault here.
>
>
> -- 
>
> paolo dot carlini at oracle dot com changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                 CC|                            |dannysmith at users dot
>                   |                            |sourceforge dot net
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40802
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40802



More information about the Gcc-bugs mailing list