Hi Seemant, see the summary for the problem. Note that USE="-* build" is the Portage 1.8.9 way of saying that only the "build" USE variable should be set. It seems to mess up due to a missing uname.1 man page, probably due to the patch?
Oh, forgot to mention that I masked out -r2 for now, so -r1 will be used instead.
-r3 has problems too: gcc -O2 -mcpu=i686 -pipe -o uptime uptime.o ../lib/libfetish.a gcc -O2 -mcpu=i686 -pipe -o su su.o ../lib/libfetish.a -lcrypt gcc -O2 -mcpu=i686 -pipe -o stty stty.o ../lib/libfetish.a make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/src' Making all in doc make[2]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/doc' Updating ./version.texi cd . \ && makeinfo --no-split `echo sh-utils.texi | sed 's,.*/,,'` make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/doc' Making all in man make[2]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/man' Updating man page uname.1 /bin/sh: /missing: No such file or directory make[2]: *** [uname.1] Error 1 make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/man' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11' make: *** [all-recursive-am] Error 2 make all-recursive make[1]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11' Making all in lib make[2]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/lib' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/lib' Making all in intl make[2]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/intl' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/intl' Making all in src make[2]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/src' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/src' Making all in doc make[2]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/doc' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/doc' Making all in man make[2]: Entering directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/man' Updating man page uname.1 /bin/sh: /missing: No such file or directory make[2]: *** [uname.1] Error 1 make[2]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11/man' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sh-utils-2.0.11-r3/work/sh-utils-2.0.11' make: *** [all-recursive-am] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 9, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/sys-apps/sh-utils/sh-utils-2.0.11-r3.ebuild .
Since sh-utils is a core package, please mask your new versions in package.mask until they are confirmed working.
It turns out that a new patch was posted to LKML last week. It also only touches the uname.c file and uses the info from /proc in a much more efficient manner than the nuname patch. I have checked in a new version of sh-utils -- it passed all the tests on my box here.