Summary: | using distcc for configure stage is slow | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Amiel Martin <martina3> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | CC: | radek |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Amiel Martin
2005-01-28 02:24:19 UTC
The easiest way to do it is to just have localhost as the first machine in your distcc hosts list. that way all config stuff is sent to the local machine as normal. distcc doesn't do configure....it only does compiling...Configuring packages on machines that you aren't running it on would be useless...INVALID? Er, you meant the compiling of the tests for configure, my bad ;) Comment #1 is probably the solution here. You could try modifying econf, but then you'd miss any ebuild that doesn't use econf, which means you'd still have problems on certain packages. |