On 04/24/15 14:56, Ian Stakenvicius wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 24/04/15 02:42 PM, Ciaran McCreesh wrote:
On Fri, 24 Apr 2015 21:12:32 +0300 Maxim Koltsov
<maksbo...@gentoo.org> wrote:
Hello. My previous email was sent from the wrong address and it
seems it did not make it into the list. Sending again from the
right address...
I'm introducing "c++14" use flag to every package in
app-leechcraft catherogy via leechcraft.eclass. I need to put USE
description somewhere. I propose / ask for permission to do it in
global use.desc. Putting this flag to every single metadata.xml
feels just wrong --- there are 72 of them now.
Proposed description: "Build using C++ 14 standard"
Looking forward for comments.
This isn't going to be sustainable... What's the long-term plan
for dealing with this?
Sounds like we need to go through the archives and revisit the
conversations about how to integrate c++11 , again..
Yes, this is going to be a perpetual problem in Gentoo. So right now,
c++03 is stable and its abi is not going to change. c++11 is stable in
gcc 5 and c++14 is experimental. Next will come c++17. The way gcc is
dealing with this is that it is NOT bumping the soname so we can get
libraries linking aginst libstdc++.so with the wrong abi and you get
breakage. I wrote a blog entry [1] and opened a tracker [2]. That bug
currently reads "[TRACKER] c++11 abi incompatibility" but we could
expand it to include c++14 and beyond.
I'm not sure how to solve this one, but a USE flag isn't going to work,
at least not in the long run.
Ref.
[1]
https://blogs.gentoo.org/blueness/2015/03/10/the-c11-abi-incompatibility-problem-in-gentoo/
[2] https://bugs.gentoo.org/show_bug.cgi?id=542482
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlU6kfYACgkQ2ugaI38ACPCDuQEAhAv0boCkTU3RvT5d/fX3la7V
8so0wqnPtHKI4fSqEwgA+wXmVlB14ykbTQ1VnrRR5WrEPRjMbm9V1MSXAA6MnC43
=i/3U
-----END PGP SIGNATURE-----
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : bluen...@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
