public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Harvesting failed compilation...
Date: Wed, 6 Dec 2017 08:38:06 +0200	[thread overview]
Message-ID: <p0837r$s9t$1@blaine.gmane.org> (raw)
In-Reply-To: <20171205160840.xbivk63rbhb3nufc@solfire>

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.



      reply	other threads:[~2017-12-06  6:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 16:08 [gentoo-user] Harvesting failed compilation tuxic
2017-12-06  6:38 ` Nikos Chantziaras [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='p0837r$s9t$1@blaine.gmane.org' \
    --to=realnc@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox