I think the summary basically says it all. I have been playing around with the new version of portage, and I absolutely love the new --jobs feature that it provides. Just awesome. However something happens that causes it to revert back to compiling 1 package at a time whenever it gets to mpfr. For example, when doing an "emerge -e world" It will go down the list and compile as many packages in parallel as possible, until it gets to mpfr.Then after that it reverts back to compiling in serial again. I've verified this like 6 times on 4 different computers. It does it on old installations, and new installations,.I've tried rc6, rc7, and now rc8, and in all cases the problem persists. Seeing as how I've got over 700 packages installed, and mpfr is only about number 60, most of the packages still compile in serial due to this bug. Reproducible: Always Steps to Reproduce: 1.emerge -e world or 2.emerge -e system or 3.pull something in that uses mpfr as a dependency Actual Results: mpfr causes portage to revert back to compiling one package at a time. Expected Results: Portage should continue to compile as many packages in parallel as is possible
Created attachment 163655 [details, diff] more parallellization This patch has been in svn for awhile and it's well tested.
Silly question... How do apply that patch? Can I add an epatch line to the ebuild? Sorry I'm not a programmer. I know next to nothing about these things.
If the patch is saved as /tmp/more_parallellization.patch, then it can be applied as follows: patch /usr/lib/portage/pym/_emerge/__init__.py /tmp/more_parallellization.patch
OK, I applied the patch and it seems to have done the trick. Problem is now solved. Thank you so much for your patience with me. I'll mark this bug as solved.
