Am 03.06.2015 um 22:32 schrieb Ciaran McCreesh: > On Wed, 03 Jun 2015 22:22:39 +0200 >> i've just hit the constraint CHECKREQS_MEMORY=3G in >>> =www-client/chromium-44.* on a 2 GiB RAM machine.. (having >>> additionally >> 5G Swap on SSD..) >> >> I personally doubt that check-reqs_memory() in the eclass should only >> check for *physical* rather than *virtual* RAM to fulfill this >> constraint and fail if unsatisfied. > > Swap is horrifically slow. It's better to fail than to use swap for > stuff... > (basically) agreed - but in distcc/icecream/whatever builds, linking *may* also be done on remote machines, which *may* fulfill the memory constraint.. we're talking about *build* constraints rather than *run* constraints, right..?
Christian
signature.asc
Description: OpenPGP digital signature
