From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 9C86D138825 for ; Wed, 12 Nov 2014 02:07:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 40A0DE08C4; Wed, 12 Nov 2014 02:07:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D4B01E0804 for ; Wed, 12 Nov 2014 02:07:48 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id E80A4340541 for ; Wed, 12 Nov 2014 02:07:47 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -2.57 X-Spam-Level: X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5.5 tests=[AWL=0.567, BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eTsUNoqWM1BD for ; Wed, 12 Nov 2014 02:07:40 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id C4FAA340540 for ; Wed, 12 Nov 2014 02:07:39 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XoNLK-0003u9-O7 for gentoo-user@gentoo.org; Wed, 12 Nov 2014 03:07:35 +0100 Received: from rrcs-71-40-157-251.se.biz.rr.com ([71.40.157.251]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Nov 2014 03:07:34 +0100 Received: from wireless by rrcs-71-40-157-251.se.biz.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Nov 2014 03:07:34 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: James Subject: [gentoo-user] Re: gcc 4.7.3 --> 4.8.3 Date: Wed, 12 Nov 2014 02:07:23 +0000 (UTC) Message-ID: References: <9194407.LW02KBNQ1l@wstn> <20141110222302.6adfe4ef@digimed.co.uk> <5461DC1A.80503@gmail.com> <20141111210356.6326a0e9@digimed.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 71.40.157.251 (Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1) X-Archives-Salt: d57c88ad-2c26-40b8-a9f6-57a76a29f750 X-Archives-Hash: 9abdb11a80981b0a2efd7920ef43d0e3 > > > Neil Bothwick wrote: > > > > After an emerge -e world, a reboot is probably best, another > > > > reason to avoid the unnecessary step of emerge -e 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