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 1Fo9pW-0006pN-U8 for garchives@archives.gentoo.org; Thu, 08 Jun 2006 02:01:03 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k581xLdL009029; Thu, 8 Jun 2006 01:59:21 GMT Received: from mail.nucoretech.com (mail.nucoretech.com [12.146.132.130]) by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k581owOI017493 for ; Thu, 8 Jun 2006 01:50:59 GMT Received: from paris ([192.9.200.83]) by mail.nucoretech.com (8.13.1/8.13.1) with SMTP id k581oqEP010532 for ; Wed, 7 Jun 2006 18:50:54 -0700 From: "Bob Young" To: Subject: RE: [gentoo-user] gcc-4.1.1 Date: Wed, 7 Jun 2006 18:50:55 -0700 Message-ID: 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 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 In-Reply-To: <7573e9640606071625i4082dd14p6c66082f503a4ae9@mail.gmail.com> Importance: Normal X-Scanned-By: milter-bcc/0.12.85 (mail.nucoretech.com [192.9.200.22]); Wed, 07 Jun 2006 18:50:54 -0700 X-Archives-Salt: a12e0c85-b2d6-4fe3-97d3-f02f75b38ee1 X-Archives-Hash: 83fbe0360ec93a8ff660c1f83bb0f6e9 > On 6/7/06, Roy Wright wrote: > > You might want to read: > > > > http://forums.gentoo.org/viewtopic.php?t=282474&highlight= > > > > which basically recommends: > > > > emerge -s > > emerge -s > > emerge -e > > emerge -e > > > Ugh, this is completely pointless. A single "emerge -e world" is > sufficient. > Depends on what you consider sufficient. Although what the page recommends was misquoted, it actually suggests: emerge -e system emerge -e system emerge -e world emerge -e world That's probably is a little bit excessive, but the reason for doing the two emerge -e systems is so that the new tool chain is built with the new tool chain. At the end of the first emerge -e system you may have a new compiler, but that new compiler was built with the old compiler. What you actually want is a gcc-4.1.1 that was built with gcc-4.1.1. You could emerge the compiler twice before doing the emerge -e system, but the the emerges that happen before glibc is rebuilt are linked against a glibc that was built with the old compiler. Same with the rest of the tool chain and libraries. That being said "emerge -e system" is probably overkill just for a new toolchain. Updating a subset of all possible toolchain related things and then following that by a single emerge -e world would probably be sufficient for most people. This page: http://forums.gentoo.org/viewtopic-t-345229.html is about doing an install, but it shows how to update a subset of the entire tool chain. Note that the article does in the end, do a double emerge -e system, so the the value of updating a toolchain subset is questionable for the article's purposes. In short: emerge gcc-config glibc binutils libstdc++-v3 gcc emerge gcc-config glibc binutils libstdc++-v3 gcc emerge -e world To be clear, in order to make sure absolutely everything is updated and the libraries that are linked against are also updated prior to use, the two emerge -e system commands, are the definitive solution. For those who don't want to spend many extra hours of compile time, in order to gain a 0.5% increase in performance, the above is offered for consideration. Regards, Bob Young -- gentoo-user@gentoo.org mailing list