Thanks! I like this option for those builds I do as a one-off.<div><br></div><div>Comer<br><br>On Wednesday, May 25, 2016, Adam Dershowitz <<a href="mailto:dersh@alum.mit.edu">dersh@alum.mit.edu</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><br></div><div><br></div>
</div>
<br><div><blockquote type="cite"><div>On May 25, 2016, at 5:25 PM, Brandon Allbery <<a href="javascript:_e(%7B%7D,'cvml','allbery.b@gmail.com');" target="_blank">allbery.b@gmail.com</a>> wrote:</div><br><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, May 25, 2016 at 5:22 PM, Christopher Jones <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','jonesc@hep.phy.cam.ac.uk');" target="_blank">jonesc@hep.phy.cam.ac.uk</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">you don’t. Its automatic for the ports that allow it.</blockquote></div><br>And this is also true, if that was not clear. Using multiple cores is *on by default*. You are already getting it, unless you at some point in the past overrode buildmakejobs in macports.conf.<br clear="all"><div><br></div>-- <br></div></div></div></blockquote></div><br><div><br></div><div>You can also manually change it for a single install, for example by using <a href="http://build.jobs" target="_blank">build.jobs</a>. Such as:</div><div>sudo port install port_whatever_name <a href="http://build.jobs" target="_blank">build.jobs</a>=4 </div><div>and then, for that specific install it will attempt to use 4 cores. This can be handy to reduce the number of cores used, from the default, so that you can do other things on the machine while building. </div></div></blockquote></div>