This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: v*printf functions not available with g++ -std=c++0x
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 18 Aug 2011 16:33:29 +0200
- Subject: Re: v*printf functions not available with g++ -std=c++0x
- References: <4E4BD899.4070409@cs.utoronto.ca>
- Reply-to: cygwin at cygwin dot com
On Aug 17 11:04, Ryan Johnson wrote:
> Hi all,
>
> I'm using the experimental gcc-4.5 package and hit a strange error:
> c++0x mode suppresses the definition of the v*printf() family of
> functions in stdio.h in c++0x mode. The offending code seems to be:
>
> #if !defined(__STRICT_ANSI__) || (__STDC_VERSION__ >= 199901L)
> #ifndef _REENT_ONLY
> ...
> int _EXFUN(vsnprintf, (char *, size_t, const char *, __VALIST)
> _ATTRIBUTE ((__format__ (__printf__, 3, 0))));
> ...
> #endif
> #endif
>
> Running `g++ -std=c++0x -dM -E' indicates that __STRICT_ANSI__ is
> defined while _REENT_ONLY and __STDC_VERSION__ are not.
>
> Oddly, functions like _vsnprintf_r are still available for some
> strange reason (aren't they extensions?). I hope this is a bug
> rather than a requirement of the new standard; meanwhile, using
> std=gnu++0x works around the problem.
If I try that with Yaakov's 4.5.3 cross compilers, then __STRICT_ANSI__
is not defined with -std=c__0x, unless I also specify `-ansi' on the
command line. However, there's a weird warning:
$ i686-pc-cygwin-g++ -std=c++0x -dM -E - < /dev/null | grep ANSI
cc1: warning: command line option "-std=c++0x" is valid for C++/ObjC++ but not for C
Well, sure, that's why I called g++, not gcc...
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple