Date: Wed, 12 Dec 2018 21:25:04 +0100 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org, freebsd-ports@freebsd.org Subject: Re: How much memory to compile www/chromium? Message-ID: <20181212202504.4n3mhtx7grbeh6j7@squirrel.exwg.net> In-Reply-To: <20181212192115.GA85583@www.zefox.net> References: <20181212165313.GA84881@www.zefox.net> <20181212184149.ol44fon2unowu35q@squirrel.exwg.net> <20181212192115.GA85583@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
## bob prohaska (fbsd@www.zefox.net): > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS"). > > > Thank you, I think that's the information needed. Come to think of it, > will the -j option, such as -j2, work in this situation also? Two threads > are much better than one 8-) If you had looked into bsd.port.mk yourself... right below the docs of DISABLE_MAKE_JOBS (line 814) is some documentation for MAKE_JOBS_NUMBER and MAKE_JOBS_NUMBER_LIMIT. -j won't help because there's a lot of arguments sanitizing going on - we can't be having with random arguments showing up down in the port's make invocations - quite often, it's not even "our" make down there. Regards, Christoph -- Spare Space.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181212202504.4n3mhtx7grbeh6j7>