This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/34032] -std=c++0x causes undeclared symbols errors on cygwin
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Nov 2007 19:33:51 -0000
- Subject: [Bug libstdc++/34032] -std=c++0x causes undeclared symbols errors on cygwin
- References: <bug-34032-13491@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from pcarlini at suse dot de 2007-11-08 19:33 -------
Ok, at least we have a work around, then. About Cygwin, probably the reason is
that those features are made available as extensions not at C99 facilities (I'm
sure that this was the case at some point for many snprintf implementations,
for example). The safe approach, then, would be always running all the autoconf
tests with the strict C++ compiler (-std=c++98, whereas -std=gnu++98 is the
default). Are there any opinions about that?
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bkoz at redhat dot com
Status|UNCONFIRMED |NEW
Component|c++ |libstdc++
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-11-08 19:33:51
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34032