[gentoo-user] Harvesting failed compilation...

[gentoo-user] Harvesting failed compilation...

[tuxic]

Hi,

after emerge -e @world --keepgoing
I got this packages, which failed to compile, listed

 * The following 11 packages have failed to build, install, or execute
 * postinst:
 * 
 *  (sys-devel/make-4.2.1-r1:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sys-devel/make-4.2.1-r1/temp/build.log'
 *  (sys-libs/glibc-9999:2.2/2.2::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sys-libs/glibc-9999/temp/build.log'
 *  (media-sound/aacgain-1.9-r1:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/media-sound/aacgain-1.9-r1/temp/build.log'
 *  (sys-libs/libstdc++-v3-3.3.6-r1:5/5::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sys-libs/libstdc++-v3-3.3.6-r1/temp/build.log'
 *  (dev-util/kbuild-0.1.9998_pre20171020:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/dev-util/kbuild-0.1.9998_pre20171020/temp/build.log'
 *  (app-misc/screen-4.6.0:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/app-misc/screen-4.6.0/temp/build.log'
 *  (net-fs/autofs-5.1.3:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/net-fs/autofs-5.1.3/temp/build.log'
 *  (app-cdr/cdrdao-1.2.3-r4:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/app-cdr/cdrdao-1.2.3-r4/temp/build.log'
 *  (sci-visualization/opendx-4.4.4-r6:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/sci-visualization/opendx-4.4.4-r6/temp/build.log'
 *  (media-gfx/meshlab-2016.12:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/media-gfx/meshlab-2016.12/temp/build.log'
 *  (media-sound/pulseaudio-11.1:0/0::gentoo, ebuild scheduled for merge), Log file:
 *   '/var/tmp/portage/media-sound/pulseaudio-11.1/temp/build.log'

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.

Somehow frustrated,
Meino

[gentoo-user] Re: Harvesting failed compilation...

[Nikos Chantziaras]

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.