| 1 |
Dnia 2015-06-03, o godz. 22:39:10 |
| 2 |
Christian Bricart <christian@×××××××.de> napisał(a): |
| 3 |
|
| 4 |
> Am 03.06.2015 um 22:32 schrieb Ciaran McCreesh: |
| 5 |
> > On Wed, 03 Jun 2015 22:22:39 +0200 |
| 6 |
> >> i've just hit the constraint CHECKREQS_MEMORY=3G in |
| 7 |
> >>> =www-client/chromium-44.* on a 2 GiB RAM machine.. (having |
| 8 |
> >>> additionally |
| 9 |
> >> 5G Swap on SSD..) |
| 10 |
> >> |
| 11 |
> >> I personally doubt that check-reqs_memory() in the eclass should only |
| 12 |
> >> check for *physical* rather than *virtual* RAM to fulfill this |
| 13 |
> >> constraint and fail if unsatisfied. |
| 14 |
> > |
| 15 |
> > Swap is horrifically slow. It's better to fail than to use swap for |
| 16 |
> > stuff... |
| 17 |
> > |
| 18 |
> (basically) agreed - but in distcc/icecream/whatever builds, linking |
| 19 |
> *may* also be done on remote machines, which *may* fulfill the memory |
| 20 |
> constraint.. |
| 21 |
|
| 22 |
Nay, linking is always done locally. |
| 23 |
|
| 24 |
And even if you were right, this isn't a lottery. It ain't 'let's let |
| 25 |
user dumbly waste 4 hours, maybe it will link for him this time'. |
| 26 |
|
| 27 |
-- |
| 28 |
Best regards, |
| 29 |
Michał Górny |
Archives