BTW, is there a special switch needed in make.conf to avoid a parallel rust compiling or is -j1 enough ? init,1 └─sudo,3136 /opt/tb/bin/chr.sh /home/tinderbox/run/13.0-desktop_test_20171027-180434 /bin/bash /tmp/job.sh └─chr.sh,3145 /opt/tb/bin/chr.sh /home/tinderbox/run/13.0-desktop_test_20171027-180434 /bin/bash /tmp/job.sh └─su,3193 - root -c /bin/bash /tmp/job.sh └─bash,3199 /tmp/job.sh └─emerge,21656 -b /usr/lib/python-exec/python3.4/emerge --update dev-util/cargo └─sandbox,27864,portage /usr/lib/portage/python3.4/ebuild.sh compile └─ebuild.sh,28017 /usr/lib/portage/python3.4/ebuild.sh compile └─ebuild.sh,28079 /usr/lib/portage/python3.4/ebuild.sh compile └─python2.7,28180 x.py build └─python2.7,27395 x.py build └─bootstrap,27397 build └─cmake,10572 --build . --target install --config Release -- -j 12 └─gmake,10577 -j 12 install └─gmake,10590 -f CMakeFiles/Makefile2 all ├─gmake,10741 -f lib/MC/CMakeFiles/LLVMMC.dir/build.make lib/MC/CMakeFiles/LLVMMC.dir/build │ ├─c++,22577 -DGTEST_HAS_RTTI=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_L
*** This bug has been marked as a duplicate of bug 626080 ***