Re: [gentoo-dev] Re: moving gcc-5.2 to unstable
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
Re: [gentoo-dev] Re: moving gcc-5.2 to unstable
On Fri, Oct 2, 2015 at 4:21 AM, Ryan Hillwrote: > On Thu, 1 Oct 2015 09:49:47 -0400 > Mike Frysinger 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?
[gentoo-dev] Re: moving gcc-5.2 to unstable
On Thu, 1 Oct 2015 09:49:47 -0400 Mike Frysingerwrote: > 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. 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. -- Ryan Hillpsn: dirtyepic_sk gcc-porting/toolchain/wxwidgets @ gentoo.org 47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 pgpIF6xgcchnn.pgp Description: OpenPGP digital signature
Re: [gentoo-dev] Re: moving gcc-5.2 to unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/2/2015 10:27 AM, Mike Gilbert wrote: > On Fri, Oct 2, 2015 at 4:21 AM, Ryan Hill> wrote: >> On Thu, 1 Oct 2015 09:49:47 -0400 Mike Frysinger >> wrote: 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? > I would propose: revdep-rebuild --library 'libstdc\+\+\.so\.6' -- --exclude sys-devel/gcc I don't think we really need to have gcc rebuild itself for the ABI change. Brian -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQIcBAEBAgAGBQJWDpg6AAoJENH3ge/59KO2jqAP/2VrtExN7vWd0M2dN9te0B0H /3tkMpxj4llQHo30oDNHISrADz/lBH1Q+c5YImQgOx+kfFMWlzqSsTS5F2KlnOHl lpYJu3BQ24wh5R84PagHbf2FpKZm8d50pN4dH0n0fry9A/khZxnLfDjpjuTTdHLN GWNl4HWdcMyVlFv/Hj8Yx4PVamgF7XqJsu+gD0reawNimjudgOq8q3Q4fUHhK1/0 1znKYRknA0DfSWUmyX8NTPkBaqYEBnB0aD/QZ9tcWXeR6F9+mCkmkNtCR6J3ds4B DzXqWjGH5ZpT1DO4bsyh+X2AoLd4j5DzIJT3pNPW/PUya3O3yH2r6gJhYXxolf/s lLJi10aYLFEwswZ4ZcjkgOQCti8Xvn6fK1/D/EC8MUmUnWYogNS2ulf2/iUlU01q JH+MLdE76j0KGa1vJNJN8fB6z7CuoOsLY/q7FNrVR3XXsyMKPoIxmsyPFfXX+y07 SWnO3tGLfZ+q82SvnX40ynnGPdl9Sp6nu/fya7liKjmtijdWNW9ZNpfw/qLGNJyb +CT5qnzRitfVwRr1CgY9K7ZCTCdLs8Qw4VkJHk+QNH5ggMsvA651MyCJZmUJ6lRN 1KEVAsT29U1nVo+oMQggj3VMY5Lqvk0Fe8ScF2unS4ts32/udlareWHK6o1T5PcU /7+orcUb1IODrKlfADrc =pkRt -END PGP SIGNATURE-