Filing to keep track. Needed for gcc-10. Please CC-arches when you are ready. Thanks!
https://gitweb.gentoo.org/repo/gentoo.git/commit/app-arch/dump?id=8e061364b8c461419cbf03aaa7a98b691cbe580b fixes .46-r1, not .47?
(In reply to Sam James from comment #1) > https://gitweb.gentoo.org/repo/gentoo.git/commit/app-arch/ > dump?id=8e061364b8c461419cbf03aaa7a98b691cbe580b fixes .46-r1, not .47? Yeah I just opened this bug a bit before dilfridge added -fcommon to .46-r1, .47 is also fixed, but I guess this isn't blocking gcc-10-stable anymore :)
(In reply to Jakov Smolic from comment #2) > (In reply to Sam James from comment #1) > > https://gitweb.gentoo.org/repo/gentoo.git/commit/app-arch/ > > dump?id=8e061364b8c461419cbf03aaa7a98b691cbe580b fixes .46-r1, not .47? > > Yeah I just opened this bug a bit before dilfridge added -fcommon to .46-r1, > .47 is also fixed, but I guess this isn't blocking gcc-10-stable anymore :) Does .47 build, given vapier's comment?
(In reply to Sam James from comment #3) > (In reply to Jakov Smolic from comment #2) > > (In reply to Sam James from comment #1) > > > https://gitweb.gentoo.org/repo/gentoo.git/commit/app-arch/ > > > dump?id=8e061364b8c461419cbf03aaa7a98b691cbe580b fixes .46-r1, not .47? > > > > Yeah I just opened this bug a bit before dilfridge added -fcommon to .46-r1, > > .47 is also fixed, but I guess this isn't blocking gcc-10-stable anymore :) > > Does .47 build, given vapier's comment? Yes
Brilliant, thanks!