From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gcc 4.7.3 --> 4.8.3
Date: Wed, 12 Nov 2014 02:07:23 +0000 (UTC) [thread overview]
Message-ID: <loom.20141112T030631-267@post.gmane.org> (raw)
In-Reply-To: 20141111210356.6326a0e9@digimed.co.uk
> > > 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...
>
Re: [gentoo-dev] more help needed with gcc-4.8 stabilization
It's a long thread, and not the ony one that hints at issues
of installing 4.8.x and still having 4.7.3 set as the default.
"webkit-gtk" was one that took me a few tries to get to compile
completely. ymmv.
Obviously many things have been resolved that are listed in the thread.
" have you considered to stabilize gcc:4.9 instead possibly 4.9.2 ?
I'm not really suggesting to do so, but seem that most of the problems
of 4.9.1 are the same of 4.8.3 so maybe it's worth considering. "
that said 4.8.3 is marked stable by the devs, but a large part of that
is 4.9.x is needed by some "key" codes coming down the pipe. No, I did
not write thus down, just made myself a mental note up upgrade everything
to 4.8.3 in preparation for 4.9.x. (Chrome is on, I think).
> > > 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.
Um, Tomas's little one-liner:
lsof -n | grep 'DEL.*lib'
revealed far to much to deal with. I got lib issues coming out of my arse
(I've been hacking at a few things I do not fully understand
(wink wink :: nudge nudge) ?
> 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.
Granted. My need to reboot is because I've been noodling around with
many many things. My current desktop: lxde is crippled and deprecated.
Lx1t-0.8.0 is in the tree now, but masked waiting on another package
or 2 to be tweaked.
> 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.
OK, so I reboot workstations more often than you. I hope that does
not upset you? Yes, I've kept workstations online for over a year more
times that I can count (fingers and toes). And when the reboot comes, It's a
day or 2 fixing things, imho. YMMV. A judicious reboot now and again, timed
well, is keenly a good idea, imho. ymmv. Besides I'm an old FT via
redundancy, kind of guy; aka I *always* have spare systems, ready to go.
On the server side. When I have to be "responsible" for servers others
use, I *always* have duplicated hot spares, or I don't do it. I'm not
saying that other should/have to do what I do. I'm very lazy and only
get lucky when it counts. No I'm too forgetful to be considered smart
anymore. So, I use spare hardwares, boot them up and away I go! I live
in Florida; so the power failures can "jump" UPS's, ethernet cables and
all sorts of strange issues, not just admin issues dictace FT via
redundancy for me. I may just move my shop onto a sail boat, so then
I'd have metal_chloride issuse to deal with......
So, via hardware redudancy, as thecomplete system level, I can
diagnose failures at my liesure, sipping coffee, wine
or a beverage that would make Alan crazy (quite a few of these....).
I deeply appreciate your concerns over the admin skills of an old_fart....
RFC 5798.
cheers?
James
next prev parent reply other threads:[~2014-11-12 2:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 17:46 [gentoo-user] gcc 4.7.3 --> 4.8.3 James
2014-11-07 18:19 ` Mark Pariente
2014-11-08 19:08 ` Stefan G. Weichinger
2014-11-08 22:39 ` Volker Armin Hemmann
2014-11-07 19:01 ` Todd Goodman
2014-11-08 16:17 ` [gentoo-user] " Nikos Chantziaras
2014-11-08 19:55 ` James
2014-11-09 9:59 ` Peter Humphrey
2014-11-10 18:52 ` James
2014-11-10 22:23 ` Neil Bothwick
2014-11-11 6:04 ` Tomas Mozes
2014-11-11 21:12 ` James
2014-11-11 9:51 ` Dale
2014-11-11 20:19 ` James
2014-11-11 21:03 ` Neil Bothwick
2014-11-11 21:27 ` Mick
2014-11-12 2:07 ` James [this message]
2014-11-12 10:18 ` Neil Bothwick
2014-11-14 4:52 ` Jonathan Callen
2014-11-14 9:55 ` Neil Bothwick
2014-11-12 5:58 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20141112T030631-267@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox