On 03 Oct 2015 19:53, Anthony G. Basile wrote:
> On 10/3/15 7:16 PM, hasufell wrote:
> > On 10/03/2015 04:13 AM, Mike Frysinger wrote:
> >> Title: GCC 5 Defaults to the New C++11 ABI
> >> Author: Mike Frysinger <vap...@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.
> >
> > They can read the docs if they don't know how.
> 
> Nothing precludes adding "see .... if you use paludis or clang." 
> However, I'd like to see the above in there.

what is the alternative suggestion for paludis ?

wrt clang, i thought we were using gcc's libstdc++ and not the libc++ project.
if people are using libc++ & clang, then this news entry does not change ...
you'd still need to rebuild anything using libstdc++.  that said, i'm not sure
libc++ & clang builds are common enough to warrant mentioning here.
-mike

Attachment: signature.asc
Description: Digital signature

Reply via email to