Date: Tue, 18 Dec 2018 23:41:44 +0000 From: Jamie Landeg-Jones <jamie@catflap.org> To: jbeich@freebsd.org, fbsd@www.zefox.net Cc: freebsd-ports@freebsd.org, freebsd-arm@freebsd.org, cmt@burggraben.net Subject: Re: How much memory to compile www/chromium? Message-ID: <201812182341.wBINfiX4052421@donotpassgo.dyslexicfish.net> In-Reply-To: <20181218174903.GA41072@www.zefox.net> References: <20181212165313.GA84881@www.zefox.net> <20181212184149.ol44fon2unowu35q@squirrel.exwg.net> <20181212192115.GA85583@www.zefox.net> <20181212202504.4n3mhtx7grbeh6j7@squirrel.exwg.net> <20181214012733.GA92808@www.zefox.net> <bm5o-wvo6-wny@FreeBSD.org> <20181218174903.GA41072@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
bob prohaska <fbsd@www.zefox.net> wrote: > Setting MAKE_JOBS_NUMBER_LIMIT=2 allowed www/chromium to compile successfully over > several days. The -DBATCH option was used, in hopes it'd fetch the right options. Use "make config-recursive" before you start. It will present to you upfront all the option screens that would appear during the build. I've noticed it sometimes misses some, if you add some dependency in one of the menus. So to be sure, once it's finished its run, if you've made any option changes, run it again, and again and again etc.. until you no longer get menus popping up. cheers, Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201812182341.wBINfiX4052421>