From c7dc3f3ea20df9c794916543b844a43b2626e504 Mon Sep 17 00:00:00 2001 From: Dan Goodliffe Date: Mon, 15 Jun 2020 11:02:44 +0100 Subject: Remove GCC link semaphore It's not the bottleneck it's believed to be, least not for me :) --- dev-util/boost-build/remove-gcc-link-semaphore.patch | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 dev-util/boost-build/remove-gcc-link-semaphore.patch diff --git a/dev-util/boost-build/remove-gcc-link-semaphore.patch b/dev-util/boost-build/remove-gcc-link-semaphore.patch new file mode 100644 index 0000000..41e2a2a --- /dev/null +++ b/dev-util/boost-build/remove-gcc-link-semaphore.patch @@ -0,0 +1,20 @@ +--- a/tools/gcc.jam 2020-06-15 10:53:45.252253351 +0100 ++++ b/tools/gcc.jam 2020-05-26 16:17:53.190885235 +0100 +@@ -1104,7 +1104,7 @@ + # Serialize execution of the 'link' action, since running N links in + # parallel is just slower. For now, serialize only gcc links, it might be a + # good idea to serialize all links. +- JAM_SEMAPHORE on $(targets) = gcc-link-semaphore ; ++#JAM_SEMAPHORE on $(targets) = gcc-link-semaphore ; + quote-rpath $(targets) ; + } + +@@ -1116,7 +1116,7 @@ + rule link.dll ( targets * : sources * : properties * ) + { + SPACE on $(targets) = " " ; +- JAM_SEMAPHORE on $(targets) = gcc-link-semaphore ; ++#JAM_SEMAPHORE on $(targets) = gcc-link-semaphore ; + quote-rpath $(targets) ; + } + -- cgit v1.2.3