1 |
On Thu, 1 Oct 2015 09:49:47 -0400 |
2 |
Mike Frysinger <vapier@g.o> wrote: |
3 |
|
4 |
> what do people want to have in place before we move gcc-5.2 into ~arch ? |
5 |
> |
6 |
> the general list looks pretty good: |
7 |
> https://bugs.gentoo.org/536984 |
8 |
|
9 |
IMO these should be fixed before we unmask: |
10 |
|
11 |
546742: x11-apps/sessreg-1.1.0 fail to build with gcc5 |
12 |
547626: dev-lang/python-3.3 / 3.4 test_faulthandler hangs with GCC 5.1 |
13 |
547950: app-shells/zsh-5.0.7-r2 builds but has runtime errors with GCC 5 |
14 |
555866: media-libs/phonon-4.8.3-r1[qt5] fails to build with gcc-5 |
15 |
|
16 |
Just because they're common packages that lots of people will have installed. |
17 |
Also they all have patches. |
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 |
FWIW I updated one system from 4.9 to 5.2 by rebuilding ~700 packages in random |
33 |
order just to see how bad the ABI breakage would be and only ran into it once. |
34 |
I may have just gotten lucky though. |
35 |
|
36 |
|
37 |
-- |
38 |
Ryan Hill psn: dirtyepic_sk |
39 |
gcc-porting/toolchain/wxwidgets @ gentoo.org |
40 |
|
41 |
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 |