| 1 |
Philip Webb wrote: |
| 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 |
> It wanted to rebuild 223 pkgs & stalled with an unfound ebuild. |
| 10 |
> |
| 11 |
> I went back to GCC 4.9.3 & the pkg merged without any problem. |
| 12 |
> |
| 13 |
> What are other users' experiences using GCC 5.4.0 ? |
| 14 |
> |
| 15 |
|
| 16 |
I just did this myself. After I switched to the new gcc, I ran |
| 17 |
revdep-rebuild. It had a large list of packages. I was planning to do |
| 18 |
a emerge -e world anyway, so I just did it instead. No sense doing most |
| 19 |
of it twice. During the rebuild, I had a qt package to fail. For some |
| 20 |
reason, it was stuck on a old qt4 version, even tho a qt5 version was |
| 21 |
there and ready to upgrade. I went ahead and manually upgraded it then |
| 22 |
restarted the emerge process again, since it didn't build many packages |
| 23 |
before that one failed anyway. It completed the whole emerge without a |
| 24 |
single failure that time. |
| 25 |
|
| 26 |
I will say this, I had to switch to Fluxbox for a while. KDE got pretty |
| 27 |
weird. I logged out, back in and it was really weird. I got a few |
| 28 |
pop-ups about things not starting correctly etc. It was unusable at |
| 29 |
that point. I then went to Fluxbox and used it for a while. Once the |
| 30 |
emerge got mostly done, KDE started working correctly again. As I |
| 31 |
suspected, some things just didn't like the difference in the gcc |
| 32 |
versions. No surprise there really. |
| 33 |
|
| 34 |
The only hitch so far, digikam is complaining with this error. |
| 35 |
|
| 36 |
digikam: symbol lookup error: /usr/lib64/libdigikamcore.so.5.5.0: |
| 37 |
undefined symbol: |
| 38 |
|
| 39 |
I'm currently rebuilding it after revdep-rebuild said it needed it. I |
| 40 |
suspect it will work once that is done. I hope so. I got pics to |
| 41 |
download from my camera. |
| 42 |
|
| 43 |
All in all, it got weird for a bit but in the end, it went fairly well. |
| 44 |
The one failure I had wasn't related to the gcc upgrade. I still have |
| 45 |
no idea why that one package was stuck on that qt4 version. For anyone |
| 46 |
using KDE and doing this, I'd do it from a console and have a time where |
| 47 |
you either have a backup desktop to use or some time to let it sit and |
| 48 |
compile and at least get most of KDE re-emerged. For me at least, KDE |
| 49 |
was unusable for a while there. |
| 50 |
|
| 51 |
It's amazing that emerge can compile about 1500 packages and not have a |
| 52 |
failure. Those devs are really doing some good work back there. :-D |
| 53 |
|
| 54 |
Oh, I skipped palemoon. I'm not using it and may unmerge it anyway. I |
| 55 |
almost forgot that one. That is talked about elsewhere in this thread. |
| 56 |
|
| 57 |
Dale |
| 58 |
|
| 59 |
:-) :-) |
Archives