Re: [gentoo-user] Re: gcc 4.7.3 --> 4.8.3

[Neil Bothwick]

On Tue, 11 Nov 2014 20:19:36 +0000 (UTC), James wrote:

> Dale <rdalek1967 <at> gmail.com> writes:
> > Neil Bothwick wrote:

> > > After an emerge -e  <at> world, a reboot is probably best, another
> > > reason to avoid the unnecessary step of emerge -e  <at> world in
> > > the first place.
>
> This conflict what others have said. Curious. My take is that since
> I updated the major compiler, gcc, it warrants an --emptytree rebuild
> and reboot, just to be safe.

Why? The compiler is not used by running software. If there was an ABI
change meaning that mixing programs compiled with the two versions would
cause problem, emerge -e would be prudent, but that hasn't happened for a
long time. You don't dismantle and reassenble your car just because you
bought a new set of spanners...

> > After I do a major upgrade or --emptytree, I switch to boot runlevel,
> > check with checkrestart and restart whatever it reports needs it.
> > Generally, switching to boot runlevel catches most everything.
>
> OK, so I emerge checkrestart and ran it. And there are almost a dozen
> things it says need a reboot (mostly lxde). "These processes do not
> seem to have an associated init script to restart them".
>
> So I have to reboot anyways.

No, simply log out of the desktop and back in.

Bear in mind that some of what checkrestart reports is unimportant
anyway. Just because a process is using a slightly older in-memory
version of a library doesn't mean it is suddenly going to stop working. I
have services that have been flagged by checkrestart for weeks that are
still fine, I just don't want to stop and restart them.

> > Yea, rebooting may be faster but I hate rebooting all the time.  :/
>
> Agreeded. But after a gcc update, I think it wise, especially since
> gcc-4.9 cometh....soon?

Yes, things may be a little different with 4.9, but the last time a
rebuild was really required was,AFAIR, somewhere around 3.3.


-- 
Neil Bothwick

Dyslexics of the world, untie!