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 To clarify - I can do this with the currently running emerge (that did not specify --keep-going)? So, when it gets to gcc (its on package # 181 of 355 now, hasn't hit either of the gcc's or glibc yet), hit ctrl-c, then: emerge --resume --skipfirst ? Do I need to add the -ev world in there? Or does emerge just know where to pick up all by itself? This is good info to have. Also - is it ok to do this during the actual compile? Or do I need to catch it before the actual compiling starts? > that's what I usually do with openoffice and similar apps when I do a > "quick" update and fail to notice the large app in there.. ;) Many thanks YoYo - this could save me a lot of time this afternoon! :) -- Charles
