Boost C++ Libraries: Ticket #12628: Build error with -no_single variant (macports) https://svn.boost.org/trac10/ticket/12628 <p> When installing boost 1.59 with single and multithread on my macOS Sierra (10.12.1) using Macports I get the following error: </p> <p> error: Name clash for '&lt;pstage/lib&gt;libboost_atomic-mt.dylib' :info:build error: :info:build error: Tried to build the target twice, with property sets having :info:build error: these incompatible properties: :info:build error: :info:build error: - none :info:build error: - &lt;dll-path&gt;/opt/local/bin :info:build error: :info:build error: Please make sure to have consistent requirements for these :info:build error: properties everywhere in your project, especially for install :info:build error: targets. :info:build :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/work/boost_1_59_0" &amp;&amp; /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/work/boost_1_59_0/b2 -d2 --layout=tagged --debug-configuration --user-config=user-config.jam -sBZIP2_INCLUDE=/opt/local/include -sBZIP2_LIBPATH=/opt/local/lib -sEXPAT_INCLUDE=/opt/local/include -sEXPAT_LIBPATH=/opt/local/lib -sZLIB_INCLUDE=/opt/local/include -sZLIB_LIBPATH=/opt/local/lib -sICU_PATH=/opt/local variant=release threading=single,multi -j8 architecture=x86 address-model=64 link=shared :info:build Exit code: 1 :error:build org.macports.build for port boost returned: command execution failed :debug:build Error code: CHILDSTATUS 32523 1 :debug:build Backtrace: command execution failed </p> <blockquote> <p> while executing </p> </blockquote> <p> "system -nice 0 $fullcmdstring" </p> <blockquote> <p> ("eval" body line 1) invoked from within </p> </blockquote> <p> "eval system $notty $nice \$fullcmdstring" </p> <blockquote> <p> invoked from within </p> </blockquote> <p> "command_exec build" </p> <blockquote> <p> (procedure "portbuild::build_main" line 8) invoked from within </p> </blockquote> <p> "portbuild::build_main org.macports.build" </p> <blockquote> <p> ("eval" body line 1) invoked from within </p> </blockquote> <p> "eval $procedure $targetname" :info:build Warning: targets not executed for boost: org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Please see the log file for port boost for details: </p> <blockquote> <p> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_boost/boost/main.log </p> </blockquote> <p> I saw online that it's not the first time this happens and that is not platform dependant. Tried some fixes with different build variants to no avail... Any suggestions? </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/12628 Trac 1.4.3 John Maddock Thu, 29 Dec 2016 11:33:35 GMT component changed; owner set https://svn.boost.org/trac10/ticket/12628#comment:1 https://svn.boost.org/trac10/ticket/12628#comment:1 <ul> <li><strong>owner</strong> set to <span class="trac-author">timblechmann</span> </li> <li><strong>component</strong> <span class="trac-field-old">None</span> → <span class="trac-field-new">atomic</span> </li> </ul> Ticket Andrey Semashev Thu, 05 Jan 2017 03:01:56 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/12628#comment:2 https://svn.boost.org/trac10/ticket/12628#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> The problem is that apparently Boost.Build cannot build both single and multi-threaded versions of Boost libraries in one go. This is not specific to Boost.Atomic, and I'm not sure whether this is an inherent Boost.Build limitation or just the way it is used in Boost libraries. I think there was a discussion of this problem on the ML some time ago. </p> <p> In order to solve the problem you have to invoke <code>b2</code> twice - first with <code>threading=single</code>, then with <code>threading=multi</code>. </p> Ticket