From: Jeffrey Walton <noloader@gmail.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: C++ and feature guards Warning Question
Date: Fri, 07 Apr 2017 21:22:00 -0000 [thread overview]
Message-ID: <CAH8yC8mA2MFYwkwpPH8+9O97cW6dYpM2c7Vs4-QBRoNLT5Bu3g@mail.gmail.com> (raw)
In-Reply-To: <ec0af940-6d74-30a4-0e8d-c81ffe449e99@oarcorp.com>
> ...
> Native GCC and glibc results:
>
> $ gcc -std=c++03 -c j.cc
> $ gcc -std=c++11 -c j.cc
> $ gcc -std=c++11 ^C j.cc
> $ gcc --version
> gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11)
>
> Suggestions on what to do to eliminate the warnings is
> appreciated.
Defining _XOPEN_SOURCE to 600 or 700 can usually squash the problems
in userland programs and libraries. I found one C++ library where it
does not.
I'm not sure how GCC will react to the define because I don't build
the compiler from sources.
Jeff
prev parent reply other threads:[~2017-04-07 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 21:18 Joel Sherrill
2017-04-05 23:39 ` Chris Johns
2017-04-06 5:26 ` Yaakov Selkowitz
2017-04-07 16:51 ` Joel Sherrill
2017-04-07 21:22 ` Jeffrey Walton [this message]
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=CAH8yC8mA2MFYwkwpPH8+9O97cW6dYpM2c7Vs4-QBRoNLT5Bu3g@mail.gmail.com \
--to=noloader@gmail.com \
--cc=joel.sherrill@oarcorp.com \
--cc=newlib@sourceware.org \
/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).