[MacPorts] #48614: boost 1.59 with -no_single failing to build
MacPorts
noreply at macports.org
Mon Feb 26 05:52:15 UTC 2018
#48614: boost 1.59 with -no_single failing to build
------------------------+------------------------
Reporter: jcverle@… | Owner: ryandesign
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.3.3
Resolution: | Keywords:
Port: boost |
------------------------+------------------------
Comment (by ryandesign):
Replying to [comment:8 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.
--
Ticket URL: <https://trac.macports.org/ticket/48614#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list