From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Why does -std=c++11 hide certain function calls
Date: Wed, 05 Sep 2018 18:46:00 -0000 [thread overview]
Message-ID: <55fcf4b3-5fd0-8fa1-6669-5a93a14c863e@t-online.de> (raw)
In-Reply-To: <CAJn6YFD-zJoH4wtDaRq1EYYLwzWv_EYFWLGm+quj_RobFMv2Dg@mail.gmail.com>
Am 05.09.2018 um 07:55 schrieb John Selbie:
> With this: g++ foo.cpp -c -std=c++11
> It compiles fine everywhere else, except CygWin. Output on Cygwin:
I'm afraid that may mean everywhere else is wrong.
> Yes, switching to -std=gnu++11 or adding -D_DEFAULT_SOURCE to the command
> line line works.
>
> But I don't understand why the need to enforce these extensions to get
> access to some of the most common unix libraries?
Because that's what std=c++11 is meant and documented to do. It turns
off all extensions to the standard language. And yes, that does include
extensions to the standard libary, up to and including POSIX-specific
content.
For what you want to do, std=c++11 is simply the wrong setting.
--
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:[~2018-09-05 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 5:56 John Selbie
2018-09-05 18:46 ` Hans-Bernhard Bröker [this message]
2018-09-05 19:36 ` John Selbie
2018-09-05 20:41 ` Brian Inglis
2018-09-06 0:14 ` Doug Henderson
2018-09-06 6:45 ` John Selbie
2018-09-06 9:18 ` Csaba Raduly
2018-09-06 14:07 ` Jeffrey Walton
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=55fcf4b3-5fd0-8fa1-6669-5a93a14c863e@t-online.de \
--to=hbbroeker@t-online.de \
--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).