<log> root@creep mail # emerge bzip2 ... gcc -fpic -fPIC -Wall -Winline -march=i686 -O3 -pipe -fomit-frame-pointer -fno-strength-reduce -D_FILE_OFFSET_BITS=64 -o bzip2-shared bzip2.c libbz2.so.1.0.2 rm -f libbz2.so.1.0 ln -s libbz2.so.1.0.2 libbz2.so.1.0 make: execvp: ln: Too many levels of symbolic links make: *** [all] Error 127 gcc -shared -Wl,-soname -Wl,libbz2.so.1.0 -o libbz2.so.1.0.2 blocksort.o huffman.o crctable.o randtable.o compress.o decompress.o bzlib.o gcc -fpic -fPIC -Wall -Winline -march=i686 -O3 -pipe -fomit-frame-pointer -fno-strength-reduce -D_FILE_OFFSET_BITS=64 -o bzip2-shared bzip2.c libbz2.so.1.0.2 rm -f libbz2.so.1.0 ln -s libbz2.so.1.0.2 libbz2.so.1.0 make: execvp: ln: Too many levels of symbolic links make: *** [all] Error 127 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 3, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/sys-apps/bzip2/bzip2-1.0.2-r2.ebuild . </log> I've tried "emerge --clean rsync" which runs fine, but doesn't resolve the problem. There aren't any symlinks pointing to each other, or any symlinks period in /var/tmp (aside from 2 which are legit from bitchx's subfolder (bitchx also get's a similar error)). Portage: Latest version Installed: 2.0.13 Do you need any other info?
I've also re-emerged fileutils.
here's what you do go into /usr/portage/sys-apps/portage/files read the README.rescue file in there and follow the instructions. then update your portage again to 2.0.13 that should fix all of this.
I extracted the file as instructed then emerge -u portage. I also did emerge --clean rsync. I then attempted to emerge bzip2. I got the same error.
I installed demarc puresecure which made a symlink to ln. This is a problem with demarc puresecure, not portage. I removed the bad symlink to ln and the problem was resolved.
