| 1 |
tastytea: |
| 2 |
> On 2022-07-07 00:19+0200 karl@××××××××.se wrote: |
| 3 |
... |
| 4 |
> > When emergings with --skipfirst (i.e. skip nodejs), |
| 5 |
> > I get: |
| 6 |
> > emerge: It seems we have nothing to resume... |
| 7 |
> > |
| 8 |
> > Checking dependancies: |
| 9 |
> > # emerge -vc net-libs/nodejs |
| 10 |
> > |
| 11 |
> > Calculating dependencies .... done! |
| 12 |
> > net-libs/nodejs-14.19.0 pulled in by: |
| 13 |
> > www-client/firefox-91.9.0 requires >=net-libs/nodejs-10.23.1 |
| 14 |
> > |
| 15 |
> > So, why don't emerge build the other 100'ish packages ? |
| 16 |
> > Last time I did emerge nodejs, must I run emerge @world |
| 17 |
> > and let that fail first ? |
| 18 |
> |
| 19 |
> Yes, --resume will always try to resume the last command that failed, |
| 20 |
> as far as i know. |
| 21 |
|
| 22 |
Just tried that, emerge world and then killing g++ once the build for |
| 23 |
nodejs started and "nodejs" failed, but emerge didn't continue with |
| 24 |
the next one (using --keep-going), so why is nodejs blocking everything |
| 25 |
else ??? |
| 26 |
|
| 27 |
So I removed firefox from world, now the rest is building. I'll solve |
| 28 |
the firefox/nodejs thing later. |
| 29 |
|
| 30 |
Regards, |
| 31 |
/Karl Hammar |
Archives