Summary: | autotools builds does not take profits of all CPU power (even with dual core) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | David Carlos Manuelda <StormByte> |
Component: | Core | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Carlos Manuelda
2007-01-30 00:22:21 UTC
Such parallelization is entirely the responsibility of the ebuilds src_compile() function. Portage has no control over it. I reopen this bug as I found a little workarround for this which works for all compilations with autotools (and thus, I changed too the caption of the bug). I tried raising the MAKEOPTS variable to test if it improves the compilations with autotools, and it indeed improves it. So I suggest handling this in portage (for example the autotools eclass, or something else) to raise in two units the number of parallel compilations. For a example, is one has MAKEOPTS="-j3", it can be set temporarily to -j4 or -j5 if autotools is being used to make current package, and revert to normal when finishing. What do you think about this little issue? I think people should look into using the -l option for MAKEOPTS instead of trying to figure out the right value for -j. Anyway I don't see how portage is involved here. |