Dale wrote: > > I just did this myself. After I switched to the new gcc, I ran > revdep-rebuild. It had a large list of packages. I was planning to do > a emerge -e world anyway, so I just did it instead. No sense doing most > of it twice. During the rebuild, I had a qt package to fail. For some > reason, it was stuck on a old qt4 version, even tho a qt5 version was > there and ready to upgrade. I went ahead and manually upgraded it then > restarted the emerge process again, since it didn't build many packages > before that one failed anyway. It completed the whole emerge without a > single failure that time. > > I will say this, I had to switch to Fluxbox for a while. KDE got pretty > weird. I logged out, back in and it was really weird. I got a few > pop-ups about things not starting correctly etc. It was unusable at > that point. I then went to Fluxbox and used it for a while. Once the > emerge got mostly done, KDE started working correctly again. As I > suspected, some things just didn't like the difference in the gcc > versions. No surprise there really. > > The only hitch so far, digikam is complaining with this error. > > digikam: symbol lookup error: /usr/lib64/libdigikamcore.so.5.5.0: > undefined symbol: > > I'm currently rebuilding it after revdep-rebuild said it needed it. I > suspect it will work once that is done. I hope so. I got pics to > download from my camera. > > All in all, it got weird for a bit but in the end, it went fairly well. > The one failure I had wasn't related to the gcc upgrade. I still have > no idea why that one package was stuck on that qt4 version. For anyone > using KDE and doing this, I'd do it from a console and have a time where > you either have a backup desktop to use or some time to let it sit and > compile and at least get most of KDE re-emerged. For me at least, KDE > was unusable for a while there. > > It's amazing that emerge can compile about 1500 packages and not have a > failure. Those devs are really doing some good work back there. :-D > > Oh, I skipped palemoon. I'm not using it and may unmerge it anyway. I > almost forgot that one. That is talked about elsewhere in this thread. > > Dale > > :-) :-) >
I wanted to add one more thing to this and see if anyone else noticed the same thing. I've mentioned before that I use several Firefox profiles. In other words, I have several instances of Firefox running at the same time doing different things. A couple or so of those can have over 100 tabs open at one time. This is something I have noticed that changed since the gcc upgrade. One, Firefox seems to use less memory. It's not a whole lot less but it is less for sure. It also uses a lot less CPU power. Used to if I had two or three Firefox profiles running, I could see 20, 30 and sometimes even more CPU usage. Gkrellm would have a good bit of orange and the little needle thing would be hovering around 30 to 40% on all the cores with it spiking to well over 50% quite a lot. Closing Firefox would put it down to single digits so I know it was Firefox causing this. Now, with 4 instances running, it is hovering around 10 to 15%. Second, I notice the same with plasmashell as well. It used to get pretty hungry on memory and CPU at times. After the upgrade, not to bad. Seems to stay about the same even after not logging out for days at a time. I did do a recent Firefox upgrade and a KDE upgrade as well. I'm not 100% sure what has the most effect on this but the two programs aren't related in any way except that they were built with the newer gcc. I found it interesting and was curious if others who upgraded have noticed anything similar to this. Maybe noticed it with other programs as well. Dale :-) :-)
