The file '/usr/lib/libcom_err.a', as provided by com_err ebuild, gets overwritten by e2fsprogs with a symlink that points to '//usr//lib/libcom_err.a', effectively creating a loop. The problem doesn't "appear", if one emerges com_err after e2fsprogs, for obvious reasons.
thanks, fixed in cvs
*** Bug 125202 has been marked as a duplicate of this bug. ***
although this was broken yesterday and fixed yesterday, its broken again. please reopen. `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. CC rehash.c `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. LD e2fsck.shared CP e2fsck make[2]: stat:../lib/libcom_err.a: Too many levels of symbolic links make[2]: *** No rule to make target `../lib/libcom_err.a', needed by `e2fsck.static'. Stop. make[2]: Leaving directory `/var/tmp/portage/e2fsprogs-1.38-r1/work/e2fsprogs-1.38/e2fsck' make[1]: *** [all-progs-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/e2fsprogs-1.38-r1/work/e2fsprogs-1.38' make: *** [all] Error 2 !!! ERROR: sys-fs/e2fsprogs-1.38-r1 failed. Call stack: ebuild.sh, line 1557: Called dyn_compile ebuild.sh, line 966: Called src_compile !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant.
(In reply to comment #3) > although this was broken yesterday and fixed yesterday, its broken again. > please reopen. it looks like i may have made a misstatement. looking at CVS, it appears that the fix referenced in comment 1 was never actually committed, and that the bug has never been fixed.
(In reply to comment #4) > it looks like i may have made a misstatement. looking at CVS, it appears that > the fix referenced in comment 1 was never actually committed, and that the bug > has never been fixed. > Re-emerge sys-libs/com_err before e2fsprogs-1.38-r1. That will fix the bad symlink from the previous installation of e2fsprogs-1.38. That worked for me.
