From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: v*printf functions not available with g++ -std=c++0x
Date: Thu, 18 Aug 2011 14:34:00 -0000 [thread overview]
Message-ID: <20110818143329.GQ27614@calimero.vinschen.de> (raw)
In-Reply-To: <4E4BD899.4070409@cs.utoronto.ca>
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
next prev parent reply other threads:[~2011-08-18 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 15:05 Ryan Johnson
2011-08-18 14:34 ` Corinna Vinschen [this message]
2011-08-28 3:36 ` Dave Korn
2011-08-29 13:56 ` Corinna Vinschen
2011-08-28 12:39 ` Ryan Johnson
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=20110818143329.GQ27614@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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: link
Be 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).