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