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