On 02 Oct 2015 02:21, Ryan Hill wrote: > 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
done > 555866: media-libs/phonon-4.8.3-r1[qt5] fails to build with gcc-5 it already has a patch that's been merged upstream, so just waiting on the kde guys to actually merge it. i don't think we need to block gcc-5 unmasking on it if it's not going to get merged any time soon. also it relies on USE=qt5 (my qt4 builds are fine). not sure the distribution of those flags in practice. > > 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. feel like writing it ? ;) > FWIW I updated one system from 4.9 to 5.2 by rebuilding ~700 packages in > random > order just to see how bad the ABI breakage would be and only ran into it once. > I may have just gotten lucky though. i upgraded gradually and it wasn't that much of a hassle, but it helps to know how to read the failing logs/symbols. so an empty world would be OK. -mike
signature.asc
Description: Digital signature
