On Sun, Apr 18, 2010 at 03:54:38PM -0400, Tanstaafl wrote: > On 2010-04-18 3:49 PM, Tanstaafl wrote: > > On 2010-04-18 1:09 PM, YoYo siska wrote: > >> On Sun, Apr 18, 2010 at 12:52:26PM -0400, Tanstaafl wrote: > >>> On 2010-04-18 12:29 PM, YoYo siska wrote: > >>>> On Sun, Apr 18, 2010 at 11:57:48AM -0400, Tanstaafl wrote: > >>>>> On 2010-04-18 11:45 AM, Johannes Kimmel wrote: > >>>>>> well... you could use --keep-going and kill something when gcc > >>>>>> compiles. not very nice, but will work without breaking > >>>>>> anything. > > > >>>>> Dang - I already started the emerge... > > > >>>> You can still break the emerge (for example with ctrl-c) when it > >>>> starts to emerge gcc, the continue the emerge process with emerge > >>>> --resume --skipfirst > > > > Worked a treat, many thanks! Saved me at least an hour of compile time... :) > > Hmmm... one last question... > > Will etc-update still prompt for all necessary changes for config files > for *all* of the installs done, considering I did ctrl-c 3 times (glibc, > and both gcc's)?
yes, if new config files got installed, etc-update will show them (I think it uses 'find' to find them ;) yoyo
