Boost C++ Libraries: Ticket #11561: Build fails with threading=single,multi

component changed; owner set

viboes — Thu, 20 Aug 2015 23:07:31 GMT

owner set to Vladimir Prus
component None → build

Adam — Tue, 16 Feb 2016 21:19:31 GMT

As a user of MacPorts, I am dealing with this problem as well. Are you working on a fix?

Vladimir Prus — Wed, 17 Feb 2016 13:41:07 GMT

I am not working on a fix; since I don't have a Mac and don't use MacPorts I have no way to reproduce this problem and investigate. In fact, I don't think that Boost uses "/opt/local/bin" anywhere.

Is there a chance this issue is reduced to a specific b2 command line, with a minimal set of libraries, and not requiring MacPorts. Output of --debug-building might also be helpful.

attachment set

ryandesign@… — Thu, 18 Feb 2016 04:06:17 GMT

attachment → main.log.bz2

build failure of boost 1.60.0 with threading=single,multi

ryandesign@… — Thu, 18 Feb 2016 04:08:55 GMT

The b2 command line that was used was given in the log file attached to the MacPorts bug report linked from the description of this ticket. I'll paste it here for easier reference:

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 link=static,shared -j4 architecture=x86 address-model=64 link=shared

I would not begin from the assumption that the problem is MacPorts-specific nor that it is OS X-specific, since, as I said, the problem did not exist with boost 1.58.0.

I have also tried with boost 1.60.0, and the issue remains. I have tried with --debug-building and have attached the log here.

Demis.john@… — Sun, 25 Feb 2018 07:11:55 GMT

Does this have anything to do with the fact that the "name clash" file has "-mt" multi-threading included, when it's trying to build a single-threaded option? I'm trying to build the +no_single option and getting the same error. I believe it's supposed to not produce the *-mt files for +no_single but not entirely sure. What does "name clash" mean?

anonymous — Sun, 25 Feb 2018 20:21:57 GMT

Correction, I meant "I'm trying to build the –no_single option" - as in it would Remove the option for No-Single processor, ie. Include the option for a Single Thread.

Replying to Demis.john@…:

Does this have anything to do with the fact that the "name clash" file has "-mt" multi-threading included, when it's trying to build a single-threaded option? I'm trying to build the +no_single option and getting the same error. I believe it's supposed to not produce the *-mt files for +no_single but not entirely sure. What does "name clash" mean?