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.54) id 1F2CE9-00081b-Nf for garchives@archives.gentoo.org; Thu, 26 Jan 2006 18:52:14 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0QIokwM017227; Thu, 26 Jan 2006 18:50:46 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0QImgL8016767 for ; Thu, 26 Jan 2006 18:48:42 GMT Received: from localhost ([127.0.0.1] helo=home.wh0rd.org) by smtp.gentoo.org with esmtp (Exim 4.54) id 1F2CAj-0001YL-WD for gentoo-dev@lists.gentoo.org; Thu, 26 Jan 2006 18:48:42 +0000 Received: (qmail 15808 invoked from network); 26 Jan 2006 13:41:14 -0500 Received: from unknown (HELO vapier) (192.168.0.2) by 192.168.0.1 with SMTP; 26 Jan 2006 13:41:13 -0500 From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Re: Re: bootstrapping since gcc 3.4 is stable Date: Thu, 26 Jan 2006 13:48:42 -0500 User-Agent: KMail/1.9 References: <200601260934.51644.mikey@badpenguins.com> <200601261716.14959.pauldv@gentoo.org> In-Reply-To: <200601261716.14959.pauldv@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601261348.42337.vapier@gentoo.org> X-Archives-Salt: 985b1148-71cf-42b5-bc0d-8b584e4728b5 X-Archives-Hash: 87722a489ce7a2bac036410857cb3703 On Thursday 26 January 2006 11:16, Paul de Vrieze wrote: > On Thursday 26 January 2006 16:34, Mikey wrote: > > And those instructions have nothing whatsoever to do with common sense > > from a new, or even experienced users perspective. Knowing that a gcc > > upgrade will break libtool is not common sense, nor is it commonly known. > > It will not break libtool. it does and it doesnt /usr/bin/libtool hardcodes the paths to internal gcc files normally this isnt an issue as most packages now generate and use their own copy of libtool so that they always have the current toolchain information a few older packages however (jpeg comes to mind) use the system libtool instead of bundling their own -mike -- gentoo-dev@gentoo.org mailing list