Summary: | need some way to restart failed compiles without unpack | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Espinoza <drinkypoo> |
Component: | Core | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | carpaski, vapier |
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Espinoza
2002-07-28 10:24:05 UTC
processors that dont cool properly is actually quite common ... one way to control it is to set the load flag in the make var MAKEOPTS="-j2 -l1.3" in this case, make wont start new compiles if the load is higher than 1.3 another thing i do is background the compile every so often to let the load drop this is kind of a bug with processors that arent cooled properly ;) There are other reasons that builds fail, power outages, for instance. The ability to resume a failed compile would be very attractive to users where the power grid fluctuates a lot. FEATURES="noauto" ebuild .... compile install merge In general this is not a good idea. SegFaults normally aren't "Oops, I broke one this one specific thing, time to die" kinds of events... It's silent corruption until it breaks something. This is not something we want to leak into the system. The above should do what you want though. FEATURES can be set in make.conf |