This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51705] Build infrastructure should not use -std=c++0x until g++ properly supports it
- From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 29 Dec 2011 21:27:18 +0000
- Subject: [Bug libstdc++/51705] Build infrastructure should not use -std=c++0x until g++ properly supports it
- Auto-submitted: auto-generated
- References: <bug-51705-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51705
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-12-29 21:27:18 UTC ---
On Thu, Dec 29, 2011 at 08:56:20PM +0000, chris at bubblescope dot net wrote:
> Better take out C++03 support as well, seeing as there is no support for the
> 'export' keyword.
>
> But seriously, the C++11 support is as complete as any other compiler, and in
> common usage. Further, parts of libstdc++ need to be built in C++0x mode.
>
Please, re-read Ed's comment #2. g++ is telling the
OS that "yes, I support C++11", when in fact it does
not. For me, this means I can no longer work on
gfortran until some work-around is in place to avoid
this bug in g++.