This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/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 18:56:44 -0000
- Subject: [Bug c++/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 #1 from pcarlini at suse dot de 2007-11-08 18:56 -------
Note that the library has autoconf tests for those C99 functions, which,
however, are run with the default C++98 compiler. Now I'm confused by this
__STRICT_ANSI__ thing on cygwin, does it mean that with -std=gnu++0x things are
fine? On gnu-linux things work in any case, simply because the glibc headers do
not disable those C99 features when -std=c++0x (or -std=c++98, for that matter)
is passed and thus __STRICT_ANSI__ is defined... I think some help from the
Cygwin people is in order...
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cgf at gcc dot gnu dot org,
| |dannysmith at users dot
| |sourceforge dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34032