| 1 |
On 02 Oct 2015 02:21, Ryan Hill wrote: |
| 2 |
> IMO these should be fixed before we unmask: |
| 3 |
> |
| 4 |
> 546742: x11-apps/sessreg-1.1.0 fail to build with gcc5 |
| 5 |
> 547626: dev-lang/python-3.3 / 3.4 test_faulthandler hangs with GCC 5.1 |
| 6 |
> 547950: app-shells/zsh-5.0.7-r2 builds but has runtime errors with GCC 5 |
| 7 |
|
| 8 |
done |
| 9 |
|
| 10 |
> 555866: media-libs/phonon-4.8.3-r1[qt5] fails to build with gcc-5 |
| 11 |
|
| 12 |
it already has a patch that's been merged upstream, so just waiting on the kde |
| 13 |
guys to actually merge it. i don't think we need to block gcc-5 unmasking on it |
| 14 |
if it's not going to get merged any time soon. |
| 15 |
|
| 16 |
also it relies on USE=qt5 (my qt4 builds are fine). not sure the distribution |
| 17 |
of those flags in practice. |
| 18 |
|
| 19 |
> > the only glaring issue is the C++11 ABI breakage: |
| 20 |
> > https://bugs.gentoo.org/542482 |
| 21 |
> > |
| 22 |
> > we already posted a news item when the breakage started in gcc-4.7: |
| 23 |
> > https://archives.gentoo.org/gentoo-dev/message/4fa0c84858b4df49668da20302fc5b6f |
| 24 |
> > |
| 25 |
> > but since gcc-5.x makes this the new default standard, more people are going |
| 26 |
> > to run into it, so we probably want a reminder. do we want any sort of |
| 27 |
> > automation otherwise here ? |
| 28 |
> |
| 29 |
> I think we need a news item to remind people they really do have to emerge -e |
| 30 |
> @world after this one or they could have a bad time. |
| 31 |
|
| 32 |
feel like writing it ? ;) |
| 33 |
|
| 34 |
> FWIW I updated one system from 4.9 to 5.2 by rebuilding ~700 packages in random |
| 35 |
> order just to see how bad the ABI breakage would be and only ran into it once. |
| 36 |
> I may have just gotten lucky though. |
| 37 |
|
| 38 |
i upgraded gradually and it wasn't that much of a hassle, but it helps to know |
| 39 |
how to read the failing logs/symbols. so an empty world would be OK. |
| 40 |
-mike |
Archives