| 1 |
On 2010-04-18 12:29 PM, YoYo siska wrote: |
| 2 |
> On Sun, Apr 18, 2010 at 11:57:48AM -0400, Tanstaafl wrote: |
| 3 |
>> On 2010-04-18 11:45 AM, Johannes Kimmel wrote: |
| 4 |
>>> well... you could use --keep-going and kill something when gcc |
| 5 |
>>> compiles. not very nice, but will work without breaking |
| 6 |
>>> anything. |
| 7 |
|
| 8 |
>> Dang - I already started the emerge... |
| 9 |
|
| 10 |
> You can still break the emerge (for example with ctrl-c) when it |
| 11 |
> starts to emerge gcc, the continue the emerge process with emerge |
| 12 |
> --resume --skipfirst |
| 13 |
|
| 14 |
To clarify - I can do this with the currently running emerge (that did |
| 15 |
not specify --keep-going)? |
| 16 |
|
| 17 |
So, when it gets to gcc (its on package # 181 of 355 now, hasn't hit |
| 18 |
either of the gcc's or glibc yet), hit ctrl-c, then: |
| 19 |
|
| 20 |
emerge --resume --skipfirst |
| 21 |
|
| 22 |
? Do I need to add the -ev world in there? Or does emerge just know |
| 23 |
where to pick up all by itself? |
| 24 |
|
| 25 |
This is good info to have. |
| 26 |
|
| 27 |
Also - is it ok to do this during the actual compile? Or do I need to |
| 28 |
catch it before the actual compiling starts? |
| 29 |
|
| 30 |
> that's what I usually do with openoffice and similar apps when I do a |
| 31 |
> "quick" update and fail to notice the large app in there.. ;) |
| 32 |
|
| 33 |
Many thanks YoYo - this could save me a lot of time this afternoon! |
| 34 |
|
| 35 |
:) |
| 36 |
|
| 37 |
-- |
| 38 |
|
| 39 |
Charles |
Archives