From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GLbHK-0001Zz-TJ for garchives@archives.gentoo.org; Fri, 08 Sep 2006 07:59:59 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k887wvlf029575; Fri, 8 Sep 2006 07:58:57 GMT Received: from cranium.sybase.co.za (sqlprd.sybase.co.za [192.96.139.1]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k887sUAX017649 for ; Fri, 8 Sep 2006 07:54:33 GMT Received: from localhost (cranium.sybase.co.za [127.0.0.1]) by cranium.sybase.co.za (Postfix) with ESMTP id 327C88344E for ; Fri, 8 Sep 2006 09:58:20 +0200 (SAST) X-Virus-Scanned: amavisd-new at sybase.co.za Received: from cranium.sybase.co.za ([127.0.0.1]) by localhost (cranium.sybase.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJmHUAVGd3lu for ; Fri, 8 Sep 2006 09:58:12 +0200 (SAST) Received: from kenster.sybase.co.za (unknown [192.168.2.135]) by cranium.sybase.co.za (Postfix) with ESMTP id 3967F8346A for ; Fri, 8 Sep 2006 09:58:12 +0200 (SAST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] gcc upgrade from 3.x to 4.x, when should I run revdep-rebuild? Date: Fri, 8 Sep 2006 09:54:14 +0200 User-Agent: KMail/1.9.4 References: In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609080954.14622.alan@linuxholdings.co.za> X-Archives-Salt: 45c977e4-7bfb-42a1-8d51-5d629f2de5a5 X-Archives-Hash: a8a2d7644e0f49eeaab05dd198a1aaf9 On Thursday 07 September 2006 23:34, michael@michaelshiloh.com wrote: > I'm upgrading my gcc from 3.x to 4.x. I've done the gcc > switching, and now I'm updating my system. > > The recommended steps are: > > # emerge -eav system > # emerge -eav world > > While emerging my system I received a message suggesting I > run revdep-rebuild: > > warning - be sure to run revdep-rebuild now > > My question is, should I run revdep-rebuild right after > emerging the system, or should I wait until after I emerge > world? My concern was that in between, my system is in an > unstable intermediate state, and it might be damaged by a > revdep-rebuild in between. There's no need to run revdep-rebuild, whatever you do it will be redundant. The notices you are seeing are primarily intended for when you explicitly emerge packages that other packages may link to. So everything that might be relevant to the notice you see is going to be recompiled anyway when you run 'emerge -e world'. As previously noted on this list, the mention of using revdep-rebuild as a shortcut when upgrading gcc was intended for the move from 3.3 to 3.4 *only*. The specifics of that upgrade made this shortcut possible, in all other upgrades you definitely don't use it. i.e. the guide is in need of an uodate to make this explicitly clear. If you need more info, ask Richard for the inside dope - he's the resident gcc expert around here :-) alan -- gentoo-user@gentoo.org mailing list