1 |
Am Sonntag, 23. April 2017, 07:45:49 CEST schrieb Philip Webb: |
2 |
> I've been following the thread re GCC 5.4.0 & after 'eix-sync' installed it. |
3 |
> There's a news item warning that there's a new ABI |
4 |
> & it mb necessary to run 'revdep-rebuild' if it fails with a linking error. |
5 |
> |
6 |
> The first pkg I tried to compile with 5.4.0 indeed failed at that point, |
7 |
> so I followed the advice & ran |
8 |
> 'revdep-rebuild --library 'llibstdc++.so.6' -- --exclude gcc'. |
9 |
> |
10 |
> What are other users' experiences using GCC 5.4.0 ? |
11 |
|
12 |
My personal advice & experience: |
13 |
* install the new gcc-5.4 |
14 |
* switch to it |
15 |
* run the revdep-rebuild command from the news item (see above) |
16 |
... and everything should be fine. |
17 |
|
18 |
To be absolutely sure I've run an "emerge -eav world" on most machines |
19 |
sometime afterwards, but that shouldnt be strictly necessary. (It helps though |
20 |
if the revdep-rebuild command doesnt finish for some reasons.) |
21 |
|
22 |
Somehow the 5.4 stabilization got stuck and/or forgotten, it's been overdue |
23 |
for a while now. Many devs (including me) use 6.3 on their main machine |
24 |
already, without any too big problems. gcc-6 is already used by the big binary |
25 |
distros. (-> Expect 6.3 to get keywords sometime soon.) |
26 |
|
27 |
-- |
28 |
Andreas K. Hüttel |
29 |
dilfridge@g.o |
30 |
Gentoo Linux developer (council, perl, libreoffice) |