From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MxiY5-0005xx-Cy for garchives@archives.gentoo.org; Tue, 13 Oct 2009 14:40:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 13F8CE0700; Tue, 13 Oct 2009 14:40:24 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by pigeon.gentoo.org (Postfix) with ESMTP id DD7A0E0700 for ; Tue, 13 Oct 2009 14:40:23 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MxiY1-0003oD-Df for gentoo-amd64@lists.gentoo.org; Tue, 13 Oct 2009 16:40:21 +0200 Received: from ip68-231-21-207.ph.ph.cox.net ([68.231.21.207]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Oct 2009 16:40:21 +0200 Received: from 1i5t5.duncan by ip68-231-21-207.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Oct 2009 16:40:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: failing to emerge update Date: Tue, 13 Oct 2009 14:39:48 +0000 (UTC) Message-ID: References: <20091013035841.GA20128@mars.lan> <225000070910122331h374f8c6ar5eb883410b83c7be@mail.gmail.com> <20091013132513.GA23274@mars.lan> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-21-207.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 41f4e5fe-22e9-4fb4-a819-508bc1583026 X-Archives-Hash: 067168bd65d249fd00b08272c8d4a228 Mansour Al Akeel posted on Tue, 13 Oct 2009 10:25:15 -0300 as excerpted: > I lost the output from the previos build, and unable to regenerate the > issue after fooliwnf libxcb update guilde. But now I am stuck with > another error, when bulllding gcc. >=20 >=20 > /var/tmp/portage/sys-devel/gcc-4.1.2/ gcc-4.1.2 ? gcc 4.1 is a bit outdated. You /may/ be able to simply=20 unmerge it. What versions of gcc do you have installed, anyway? It's=20 likely you have a 4.3 version, as gcc-4.3.2-r3 is the latest keyworded=20 stable for amd64. A caution, however. Until your whole system is rebuilt with the newer=20 gccs, some C++ packages in particular may still link to the old=20 versions. But it should at least be possible to ignore the old gccs for=20 the moment (emerge --resume --skipfirst if necessary) and build=20 everything else. If you're using FEATURES=3Dbuildpkg, it's easy enough t= o=20 unmerge a package, see if anything breaks (run revdep-rebuild and see if=20 there's anything that needs rebuilt, and hope it rebuilds fine), and=20 remerge the binpkg if necessary. That's what I'd do. =20 If you're not running FEATURES=3Dbuildpkg, I'd suggest you consider it. =20 Right before a system-wide rebuild is a great time to turn it on. =3D:^) = =20 But if you're not, you can use quickpkg to create a binpkg of a=20 particular package before removing it for testing. That way you still=20 get the binpkg, and can remerge it if necessary, if you find you still=20 need it. Anyway... after updating gcc to 4.3.2-r3 if you don't have it, and gcc- config-ing to it, you could emerge --emptytree @system @world so=20 everything is built with it, and then unmerge older gcc versions,=20 including the 4.1.2 that's giving you issues ATM. FWIW, on ~amd64, the only gcc I have currently installed is 4.4.1, as I=20 unmerged earlier versions after I had rebuilt the entire system with it. = =20 I do remember having some issues rebuilding earlier gccs at one point,=20 but with the entire system (other than those gccs) building with 4.4.1, I= =20 was able to unmerge them instead of rebuild them. Of course, I always do --update --deep --newuse, generally a couple times= =20 a week, and revdep-rebuild and --depclean afterward, to make sure the=20 system stays consistent and keep the cruft to a minimum. If you've let=20 it build up by not regularly using --update --deep and not regularly=20 doing --depcleans and revdep-rebuilds, you are likely to have quite some=20 problems getting the system back in shape, as there will be quite some=20 cruft buildup to clean out, and doing it incrementally as the updates=20 show up is MUCH easier than letting it buildup and trying to do it all at= =20 once. --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman