<div dir="ltr">John,<div><br></div><div>it's known explicitly-coded behavior. Previously, running multiple links in parallel used to kill performance rather than improve it. See:</div><div><br></div><div><pre style="margin-top:0px;margin-bottom:0px"><span style="color:#c0c0c0"> </span>JAM_SEMAPHORE<span style="color:#c0c0c0"> </span>on<span style="color:#c0c0c0"> </span>$(targets)<span style="color:#c0c0c0"> </span>=<span style="color:#c0c0c0"> </span><s>gcc-link-semaphore<span style="color:#c0c0c0"> </span>;</pre><pre style="margin-top:0px;margin-bottom:0px"><br></pre>in gcc.jam along with a comment above it. You can comment it out and see whether it improves performance. If so, it might become an option.<pre style="margin-top:0px;margin-bottom:0px"><br></pre>Thanks,<br>Volodya<br></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 25, 2015 at 1:31 PM John Maddock <<a href="mailto:jz.maddock@googlemail.com">jz.maddock@googlemail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<br> <br> I've noticed something very strange, and very annoying with mingw builds<br> - the link steps all seem to be performed serially, never in parallel -<br> is this a known issue?<br> <br> I'm using a win64 build of bjam, plus ming-x64. Building with msvc with<br> the same bjam executable works fine, as does building on Linux with GCC.<br> <br> Even if I kill the build and restart, it still runs all the remaining<br> link steps in series, and it takes an age with mingw.<br> <br> Any ideas?<br> <br> Thanks, John.<br> _______________________________________________<br> Unsubscribe & other changes: <a href="http://lists.boost.org/mailman/listinfo.cgi/boost-build" rel="noreferrer" target="_blank">http://lists.boost.org/mailman/listinfo.cgi/boost-build</a><br> <br> </blockquote></div></div>