From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] impending c++11 clusterfuck?
Date: Wed, 2 Dec 2015 02:38:36 -0500 [thread overview]
Message-ID: <565E9FFC.5020102@gentoo.org> (raw)
In-Reply-To: <20151202080637.14bfea23.mgorny@gentoo.org>
On 12/2/15 2:06 AM, Michał Górny wrote:
>
> So you're saying we should write a whole eclass to do:
>
> append-cppflags -std=c++11
>
> ?
>
I think you mean append-cxxflags. Anyhow, I had an off list discussion
with David Klaftenegger about the semantic difference between c++11 and
98 with respect to their atomics and I'm convinced that a global
-std=c++11 could get us into trouble on packages that make use of
threading. So drop my idea of global c++11 and you'll have to catch
these on a per package basis.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2015-12-02 7:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 3:56 [gentoo-dev] impending c++11 clusterfuck? Gregory M. Turner
2015-11-30 4:10 ` C Bergström
2015-11-30 8:52 ` Mikhail Korolev
2015-11-30 6:42 ` Michał Górny
2015-11-30 8:07 ` Anthony G. Basile
2015-11-30 9:52 ` Michał Górny
2015-11-30 11:17 ` Anthony G. Basile
2015-11-30 11:31 ` Anthony G. Basile
2015-11-30 18:34 ` Greg Turner
2015-11-30 18:37 ` Greg Turner
2015-11-30 22:49 ` C Bergström
2015-12-01 8:59 ` Benda Xu
2015-12-01 9:03 ` Anthony G. Basile
2015-12-01 11:25 ` Michał Górny
2015-12-01 12:18 ` Anthony G. Basile
2015-12-02 2:12 ` Gregory M. Turner
2015-12-02 7:06 ` Michał Górny
2015-12-02 7:38 ` Anthony G. Basile [this message]
2015-12-02 12:54 ` Patrick Lauer
2015-12-02 10:00 ` Gregory M. Turner
2015-12-02 12:57 ` Michał Górny
2015-11-30 10:16 ` Greg Turner
2015-11-30 10:42 ` Greg Turner
2015-11-30 9:18 ` Gregory M. Turner
2015-11-30 9:58 ` Michał Górny
2015-11-30 16:48 ` Steven Lembark
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=565E9FFC.5020102@gentoo.org \
--to=blueness@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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