From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B7861139083 for ; Wed, 6 Dec 2017 06:38:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 78B55E112B; Wed, 6 Dec 2017 06:38:05 +0000 (UTC) Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 05BB3E0F59 for ; Wed, 6 Dec 2017 06:38:04 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eMTL8-0007mC-DL for gentoo-user@lists.gentoo.org; Wed, 06 Dec 2017 07:37:54 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nikos Chantziaras Subject: [gentoo-user] Re: Harvesting failed compilation... Date: Wed, 6 Dec 2017 08:38:06 +0200 Message-ID: References: <20171205160840.xbivk63rbhb3nufc@solfire> 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=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 In-Reply-To: <20171205160840.xbivk63rbhb3nufc@solfire> Content-Language: en-US X-Archives-Salt: 6b233473-afaa-4837-910b-3188f22d6f61 X-Archives-Hash: 6fc4087f31ef53d83ca246268374c841 On 05/12/17 18:08, tuxic@posteo.de wrote: > after emerge -e @world --keepgoing > I got this packages, which failed to compile, listed > [...] > > make failed > glibc failed > libstd++ failed > > so...the less important packages so to say. > > And after fixing those -- if possible -- I guess that I doomed > to start the whole process right from the beginning. If you can fix them, portage should still remember the previous run and keep rebuilding world from where it stopped. It remembers 2 past failed emerges when using --resume. See "man emerge", in the "--resume" section. In this case, do "emerge --resume" first, but when the first package in the list starts to emerge, abort with Ctrl+C. This will count as a failed emerge and the resume list will get updated and remember that one as the most recent one. Then do a backup copy of /var/cache/edb/mtimedb. Now try and fix the packages. After you fixed them, see if "emerge --resume" still remembers the last world rebuild. If not, copy the backed up file back and now "emerge --resume" should continue building from where it last failed.