public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "scovich at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52166] New: c++0x required to import standard c++ headers? Date: Wed, 08 Feb 2012 01:19:00 -0000 [thread overview] Message-ID: <bug-52166-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52166 Bug #: 52166 Summary: c++0x required to import standard c++ headers? Classification: Unclassified Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: scovich@gmail.com Several of the standard C++ wrapper versions of C headers can only be imported with c++0x support enabled (tested on both cygwin and x86_64-linux): #error This file requires compiler and library support for the upcoming ISO C++ standard, C++0x. This support is currently experimental, and must be enabled with the -std=c++0x or -std=gnu++0x compiler options. Workaround is to #include <foo.h> instead of <cfoo>, but it's annoying given that the former is supposedly The Right Way for C++ programs to bring in the header. Affected files: ccomplex cfenv cinttypes cstdint
next reply other threads:[~2012-02-08 1:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-08 1:19 scovich at gmail dot com [this message] 2012-02-08 9:01 ` [Bug c++/52166] " redi at gcc dot gnu.org 2012-02-08 10:22 ` rguenth at gcc dot gnu.org 2012-02-08 10:58 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-52166-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).