emergeing dev-libs/icu-3.2 failed on 3 of my machines with some job-server errors. After setting MAKEOPTS="-j1" it worked. Looks like some broken Makefile dependencies. So please set either MAKEOPTS="-j1" or use "make" instead of "emake" in the ebuild. This solves the problem. thanks. Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > emergeing dev-libs/icu-3.2 failed on 3 of my machines with some job-server > errors. After setting MAKEOPTS="-j1" it worked. > > Looks like some broken Makefile dependencies. > > So please set either MAKEOPTS="-j1" or use "make" instead of "emake" in the > ebuild. This solves the problem. > > thanks. > > > Reproducible: Always > Steps to Reproduce: emerging app-shells/bash-3.0-r12 failed on my machine (within an "emerge --update --deep --newuse world") and on the machine of the gentleman posting here: http://forums.gentoo.org/viewtopic-t-375303-highlight-error+appshells+bash3+0r12.html Changing to "MAKEOPTS=-j1" allows the emerge to succeed.
fixed dev-libs/icu-3.2 ebuild is in CVS now.
app-shells/bash-3.0-r12 also fixed in CVS.
The bug has reappeared in the app-shells/bash-3.2_p17-r1 ebuild.
+ emake -j1 || die "make failed" # see bug 102426
whoops! ^^^^^^^ that's for: app-shells/bash-3.2_p17-r1:
(1) not a toolchain bug (2) this bug is not about bash at all, only icu (3) if bash is a problem for you, open a real bug with real information