From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org,hasufell <hasufell@gentoo.org>
Subject: Re: [gentoo-dev] gcc-5 news item wrt C++ ABI
Date: Tue, 06 Oct 2015 07:43:53 +0200 [thread overview]
Message-ID: <D528603B-5DD0-4E22-B918-645277540EEF@gentoo.org> (raw)
In-Reply-To: <561061E3.6070706@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dnia 4 października 2015 01:16:51 CEST, hasufell <hasufell@gentoo.org> napisał(a):
>On 10/03/2015 04:13 AM, Mike Frysinger wrote:
>> Title: GCC 5 Defaults to the New C++11 ABI
>> Author: Mike Frysinger <vapier@gentoo.org>
>> Content-Type: text/plain
>> Posted: 2015-10-02
>> Revision: 1
>> News-Item-Format: 1.0
>> Display-If-Installed: >=sys-devel/gcc-5
>>
>> GCC 5 uses the new C++ ABI by default. When building new code, you
>might run
>> into link time errors like:
>> ...: undefined reference to
>'_ZNSt6chrono12steady_clock3nowEv@GLIBCXX_3.4.17'
>> Or you might see linkage failures with "std::__cxx11::string" in the
>output.
>>
>> These are signs that you need to rebuild packages using the new C++
>ABI.
>> You can quickly do so by using revdep-rebuild like so:
>> # revdep-rebuild --library 'libstdc\+\+\.so\.6'
>>
>
>We shouldn't assume a particular PM/toolset in news items, IMO. Just
>saying that people might have to rebuild packages linked against
>libstdc++.so.6 should be enough.
Wrong. We should provide examples for the common case. Examples are often easier to comprehend than elaborate attempts of explaining what needs to be done.
>
>They can read the docs if they don't know how.
- --
Best regards,
Michał Górny
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCgAzLBxNaWNoYcWCIEfDs3JueSAoR2VudG9vKSA8bWdvcm55QGdlbnRv
by5vcmc+BQJWE1+CAAoJELB6GurvtEZOthMP/R09P/RH5SHo1QpZBmdcJrSGDgS3
6k9R/r9ddT7FbJJUgEh5/uA1ftW3f4Fp2qkGnZa5bLD/w6CKAaPDJE6ZVG/njRu9
FUkdsH5P5paGBZphR6s4WVHGNcpbovnkDJce90BkO//WzrPrqfRr1G47Q/U/rdIj
ZPb/aoOn1vj1zvX5z2x7N6PbhCCnGneRcQvdvY2vaQ7CN7exhwgucY43xIPP5YZx
c0EVJvbmpSjathH+j1fvprL/5E+58Wv14f5x8i3V/l9w3aWytGUxK4LDjOGbPs5L
OCztWZWsSes/YeQZF4OX8lc16vwCpro8PI47kgzQub8lgOARIVcyfhtl2taX8lYf
hYQXYSzpElwc5rPQeQ4/ZCLDL+JjbcjZDr3gfpBR3J14UY7vGgCUEvIPk6tDxXMf
BaSAB3JhbJ4AYRhLxnTBDAEBSioEYnHqGX5Y/U+HHBnj0WbesU3r88Df2RZuyBxD
rsoUsyXer1QMm2SoVc5P7SfGuHKeZW1F78VRirmMYpEtrUD5PgczH9UFYVVmuInE
FA/2XKfQ+noIY+sx948pvwESuxpJ40NoDbbdojFLIId3FsUUmDFLf4tuEIvMSMKM
IZhnUxzCg6DdO/BhJQK8sPRHxk7W6EaPT7wuITt/h27Ls9qjWfqAgCd2r0mJ2N9c
tNHI964xZS6TScq2
=dMvl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-10-06 5:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 13:49 [gentoo-dev] moving gcc-5.2 to unstable Mike Frysinger
2015-10-01 14:11 ` Alexandre Rostovtsev
2015-10-01 14:24 ` Mike Frysinger
2015-10-01 15:10 ` Alexandre Rostovtsev
2015-10-01 14:34 ` Georg Rudoy
2015-10-01 20:04 ` Anthony G. Basile
2015-10-02 8:21 ` [gentoo-dev] " Ryan Hill
2015-10-02 13:56 ` Mike Frysinger
2015-10-02 14:27 ` Mike Gilbert
2015-10-02 14:44 ` Brian Evans
2015-10-03 2:13 ` [gentoo-dev] gcc-5 news item wrt C++ ABI Mike Frysinger
2015-10-03 4:53 ` [gentoo-dev] " Ryan Hill
2015-10-03 5:04 ` [gentoo-dev] " Jason Zaman
2015-10-03 8:37 ` [gentoo-dev] " Ryan Hill
2015-10-03 12:38 ` [gentoo-dev] " Ciaran McCreesh
2015-10-03 17:24 ` Mike Frysinger
2015-10-03 17:30 ` Ciaran McCreesh
2015-10-05 18:43 ` Paweł Hajdan, Jr.
2015-10-06 4:43 ` Mike Frysinger
2015-10-03 23:16 ` hasufell
2015-10-03 23:53 ` Anthony G. Basile
2015-10-04 3:58 ` [gentoo-dev] " Duncan
2015-10-20 18:17 ` [gentoo-dev] " Mike Frysinger
2015-10-06 4:49 ` Mike Frysinger
2015-10-06 5:43 ` Michał Górny [this message]
2015-10-05 18:45 ` Paweł Hajdan, Jr.
2015-10-05 19:20 ` Jason A. Donenfeld
2015-10-06 4:46 ` Mike Frysinger
2015-10-17 10:07 ` Anthony G. Basile
2015-10-22 13:57 ` Mike Frysinger
2015-12-20 21:31 ` Mike Gilbert
2015-10-29 21:18 ` [gentoo-dev] moving gcc-5.2 to unstable Mike Frysinger
2015-12-09 4:28 ` [gentoo-dev] moving gcc-5.3 " Mike Frysinger
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=D528603B-5DD0-4E22-B918-645277540EEF@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hasufell@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