[Bug libstdc++/34032] -std=c++0x causes undeclared symbols errors on cygwin
pcarlini at suse dot de
gcc-bugzilla@gcc.gnu.org
Thu Nov 8 19:34:00 GMT 2007
------- 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
More information about the Gcc-bugs
mailing list