On Fri, Oct 2, 2015 at 4:21 AM, Ryan Hill <rh...@gentoo.org> wrote: > On Thu, 1 Oct 2015 09:49:47 -0400 > Mike Frysinger <vap...@gentoo.org> wrote: > >> what do people want to have in place before we move gcc-5.2 into ~arch ? >> >> the general list looks pretty good: >> https://bugs.gentoo.org/536984 > > IMO these should be fixed before we unmask: > > 546742: x11-apps/sessreg-1.1.0 fail to build with gcc5 > 547626: dev-lang/python-3.3 / 3.4 test_faulthandler hangs with GCC 5.1 > 547950: app-shells/zsh-5.0.7-r2 builds but has runtime errors with GCC 5 > 555866: media-libs/phonon-4.8.3-r1[qt5] fails to build with gcc-5 > > Just because they're common packages that lots of people will have installed. > Also they all have patches. > >> the only glaring issue is the C++11 ABI breakage: >> https://bugs.gentoo.org/542482 >> >> we already posted a news item when the breakage started in gcc-4.7: >> >> https://archives.gentoo.org/gentoo-dev/message/4fa0c84858b4df49668da20302fc5b6f >> >> but since gcc-5.x makes this the new default standard, more people are going >> to run into it, so we probably want a reminder. do we want any sort of >> automation otherwise here ? > > I think we need a news item to remind people they really do have to emerge -e > @world after this one or they could have a bad time.
I was able to get by with a targeted revdep-rebuild run. revdep-rebuild --library 'libstdc\+\+\.so\.6' The backslashes are significant since revdep-rebuild passes the expression to grep -E. Is there any reason to rebuild programs that do not link with the C++ standard library?
