Sash is a small shell, I'm not really sure what it's used for, or if it's neccessary. I'm using adm64 here, although there are reports that x86 has the same problem. But compiling sash against >=linux-header-2.6 causes it to fail, which stops emerge system. gcc -O3 -Wall -Wmissing-prototypes -DHAVE_GZIP -DHAVE_EXT2 -c -o cmd_chattr.o cmd_chattr.c In file included from /usr/include/linux/spinlock.h:16, from /usr/include/linux/blockgroup_lock.h:8, from /usr/include/linux/ext2_fs_sb.h:19, from /usr/include/linux/ext2_fs.h:20, from cmd_chattr.c:15: /usr/include/asm/processor.h:191: error: syntax error before "u16" /usr/include/asm/processor.h:193: error: syntax error before "twd" /usr/include/asm/processor.h:194: error: syntax error before "fop" Also see http://forums.gentoo.org/viewtopic.php?t=136953&highlight=sash If sash isn't required for anything (as people are just doing a emerge -i) it should be removed. I couldn't find a simple workaround
sash is a staticly compiled emergency shell that will work even if everything else on the system doesnt. yes it is needed. and you are using unsupported kernel headers that are masked on all archs.
