On 05/12/17 18:08, tu...@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.
