'emerge sync' produces this output... Portage 2.0.48: bash: line 1 usr/sbin/ebuild.sh: No such file or directory >>> Regenerating ld.so.cache... Traceback (Most recent call last): File: /usr/bin/emerge, line 1763 in ? File: /usr/bin/emerge, line 1133 in merge OSError: [Errno 2] No such file or directory Afterwards, env-update, emerge, and misc other commands are simply gone. /usr/portage/* remains, but I cannot do anything. I have tried the README.RESCUCE techniques but those didn't seem to do much of anything. Reproducible: Always Steps to Reproduce: 1. Check ln -sf whatever /etc/localtime and date 2. emerge -vp system | less 3. prompt: USE="-java -berkdb -doc" emerge system I am picky about my USE flags and I always do the method above to figure out what flags will be compiled. Note that I tried emerge system w/same flags in make.conf and no CLI flags and it's the same problem. I also untarred the stage2 tarball again (which brings back all the missing commands) but it's the same result. Actual Results: Portage 2.0.48: bash: line 1 usr/sbin/ebuild.sh: No such file or directory >>> Regenerating ld.so.cache... Traceback (Most recent call last): File: /usr/bin/emerge, line 1763 in ? File: /usr/bin/emerge, line 1133 in merge OSError: [Errno 2] No such file or directory Multiple commands disappear / become uninstalled when this error happens (emerge, env-update, some others I can't remember but thoslisted are the big ones) Expected Results: Self explanatory (Finish the emerge system w/no errors 600MHz Duron (not overclocked), 768M RAM, 2x120G WD HDDs in RAID0 using on-board Highpoint raid (boot: gentoo noscsi doataraid), boot=/dev/ataraid/disc0/part1, root=/dev/ataraid/disc0/part6, chrooted / mounted ok
*** Bug 21750 has been marked as a duplicate of this bug. ***
What stage are you starting from? Give me the output of the following before you run emerge system: emerge -v info
closing for now, can be reopened if necessary.
