I had a system freese during a merge. After reboot, emerge failed. Three times, until I think about flusing ccache. Here was the error i got: CC rotate.lo CC scale.lo CC script.lo CC span.lo CC updates.lo CC ximage.lo CCLD libImlib2.la .libs/color_helpers.o: file not recognized: File truncated collect2: ld returned 1 exit status make[3]: *** [libImlib2.la] Error 1 make[3]: Leaving directory `/var/tmp/portage/media-libs/imlib2-9999/work/imlib2/src/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-libs/imlib2-9999/work/imlib2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-libs/imlib2-9999/work/imlib2' make: *** [all] Error 2 * Using user server for live sources: http://svn.enlightenment.org/svn/e/trunk * This is a LIVE SOURCES ebuild. * That means there are NO promises it will work. * If it fails to build, FIX THE CODE YOURSELF * before reporting any issues. * ERROR: media-libs/imlib2-9999 failed: * emake failed !!! SEND BUG REPORTS TO enlightenment@gentoo.org NOT THE E TEAM * I was lucky to think about ccache. But, the error should be printed a different way. First, the gcc/ldd error message should tell that it "could" be a ccache issue. But any way, ccache should include more cheks about file validity. I am using ext4 over RAID5, with 2.6.34. I did not determine yet the reason of the freese; it happens only since a few days, since I activated my full X (I always had 3 video cards, but they were not configured yet in X); so, it may be a PSU problem being not powerfull enough. Then, I expect ext4 FS could not properly sync disks in time, or that the journal was not comitted properly. I am not saying that ccache should store CRC for every single file; but it should at least store the size of data somewhere, or make basic checks (not send empty data, or a lib that would not contain description of all functions that are listed in it's header ... ) ... ... or, when gcc fails, it should try to re-build the source once with some kind of no-cache option. I found this in 10mn, but a beginner could loose several days on this. Yes i know media-libs/imlib2-9999 is from a layman and not in portage, but, really, i don't care: this bug could have happen with any ebuild in portage.
*** This bug has been marked as a duplicate of bug 79519 ***