Summary: | get_number_of_jobs in eutils.eclass does not account for distcc hosts | ||
---|---|---|---|
Product: | Portage Development | Reporter: | John Steele Scott <toojays> |
Component: | Unclassified | Assignee: | Lisa Seelye (RETIRED) <lisa> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | CC: | bcowan |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
John Steele Scott
2003-07-25 19:06:23 UTC
i propose you just set up your MAKEOPTS in make.conf the way you should and forget about trying to make portage sufficiently smart ... but thats just me :) From asking around it seems that this function is supposed to ensure that the build will complete. The best solution would be to disable parallel makes when they fail (such in the case of Xfree and Mozilla) instead of trying to guess what -j would be the "best." I'll ask around some more to find the true intention of the function, but I'm hesitant to change it right now, without more info. That's cool, it was just a thought . . . you know, when you're compiling a big package on a slow machine, thoughts about how to improve the compile time seem really important . . . but once the package is compiled, compile time seems less important and stability moreso. I guess the real fix would be to fix the build systems for the packages which fail with high job numbers, but I suspect that'd be rather more difficult. Bug 13565 contains more discussion about this function, and a suggestion that those of us who don't like it can disable it via the portage overlay in /usr/local/portage. Right. I think the only packages that have problems with parallel makes use this function. I don't really see any reason or need to do anything with this function at this time. |