boost 1.59 with -no_single failing to build

[TBird2001 (Jason Verley)]

My boost installation uses the -no_single flag. When I do a "port upgrade" for boost, I get an error during the building stage. The errors in the log file (which I will attach) start with:

Name clash for '<pstage/lib>libboost_atomic-mt.a'

[TBird2001 (Jason Verley)]

Log file

[TBird2001 (Jason Verley)]

Forgot to mention I'm running OS X 10.10.5 on a mid-2011 MacBook Air.

[ryandesign (Ryan Carsten Schmidt)]

Confirmed. I've ​reported this problem to the developers of boost.

[ostefano (Stefano Ortolani)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #50643.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #54991.

[demisjohn (Demis D. John)]

I am trying to compile a library that asks for libboost_python, instead of libboost_python-mt (multi-threaded), so I need the "-no_single" option which still, 3 years later, fails to build in the same way as described above.

Does anyone know what causes a "name clash" error, or where to look to try and get this working?

I am looking into building the CAMFR module with the -mt option, but I suspect that is beyond my pay grade.

[demisjohn (Demis D. John)]

Looks like some think there is just a bug in the build scripts: ​https://stackoverflow.com/questions/28398390/boost-build-breaks-name-clash-for-pstage-liblibboost-system-so-1-58-0

You apparently have to specify the architecture & address-model explicitly. Any idea how to do that in macports? Maybe have Port download the boost code, and then compile manually?

[ryandesign (Ryan Carsten Schmidt)]

Replying to demisjohn:

I am trying to compile a library that asks for libboost_python, instead of libboost_python-mt (multi-threaded), so I need the "-no_single" option which still, 3 years later, fails to build in the same way as described above.

Does anyone know what causes a "name clash" error, or where to look to try and get this working?

I am looking into building the CAMFR module with the -mt library version, but I suspect this is beyond my pay grade.

It should be trivial. Wherever your other software is asking for "boost_python", change it to "boost_python-mt". The fact that this is so easy to do is one of the reasons why I haven't spent any time investigating the problem. It's the boost developers' job to investigate it, so if you want it to be fixed, you'll have to talk to them, as I see you've already done in the upstream bug report.

[ryandesign (Ryan Carsten Schmidt)]

Replying to demisjohn:

Looks like some think there is just a bug in the build scripts: ​https://stackoverflow.com/questions/28398390/boost-build-breaks-name-clash-for-pstage-liblibboost-system-so-1-58-0

You apparently have to specify the architecture & address-model explicitly. Any idea how to do that in macports?

I'm not sure that Stack Overflow post is relevant. It seems to be concerned with boost versions 1.58.0 and 1.57.0. This ticket is about a new problem that appeared in boost 1.59.0.

Maybe have Port download the boost code, and then compile manually?

That is exactly what MacPorts does.