From: "Csaba Ráduly" <rcsaba@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Symbol visibility problems with -std=
Date: Wed, 13 May 2020 15:22:18 +0200 [thread overview]
Message-ID: <7265afcc-6d95-b931-2568-ae879e1a1094@gmail.com> (raw)
In-Reply-To: <fc1d2735-da6e-95de-6c44-e163a94df843@gmail.com>
On 13/05/2020 14:12, Marco Atzeri via Cygwin wrote:
> Am 13.05.2020 um 12:21 schrieb Pavel Fedin via Cygwin:
(snip code using strdup)
>> $ g++ test.cpp -o test - compiles OK
>> $ g++ test.cpp -o test -std=c++14 - error: 'strdup' was not declared in this
>> scope; did you mean 'strcmp'?
>>
>
>
> strdup is an extension of C standard
>
> so strictly behaviour of Cgywin is correct, see
>
> /usr/include/sys/features.h
>
> for details
Pavel, you may want to try -std=gnu++14 instead.
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
next prev parent reply other threads:[~2020-05-13 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200513102124eucas1p20b619bf7b82b386c66e935199790b2c1@eucas1p2.samsung.com>
2020-05-13 10:21 ` Pavel Fedin
2020-05-13 12:12 ` Marco Atzeri
2020-05-13 13:22 ` Csaba Ráduly [this message]
2020-05-13 14:08 ` Yaakov Selkowitz
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=7265afcc-6d95-b931-2568-ae879e1a1094@gmail.com \
--to=rcsaba@gmail.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).