Opened 9 years ago

Last modified 7 months ago

#48614 assigned defect

boost 1.59 with -no_single failing to build

Reported by: TBird2001 (Jason Verley) Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: ostefano (Stefano Ortolani), adkafka@…, ksze (Kal Sze), CryptoCoding, cooljeanius (Eric Gallager)
Port: boost

Description (last modified by ryandesign (Ryan Carsten Schmidt))

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'

Attachments (1)

main.log (28.2 KB) - added by TBird2001 (Jason Verley) 9 years ago.
Log file

Download all attachments as: .zip

Change History (14)

Changed 9 years ago by TBird2001 (Jason Verley)

Attachment: main.log added

Log file

comment:1 Changed 9 years ago by TBird2001 (Jason Verley)

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

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned

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

comment:3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

comment:4 Changed 9 years ago by ostefano (Stefano Ortolani)

Cc: ostefano@… added

Cc Me!

comment:5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: adkafka@… added

Has duplicate #50643.

comment:6 Changed 8 years ago by ksze (Kal Sze)

Cc: ksze added

comment:7 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: CryptoCoding added

Has duplicate #54991.

comment:8 Changed 7 years ago by 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 library version, but I suspect this is beyond my pay grade.

Last edited 7 years ago by demisjohn (Demis D. John) (previous) (diff)

comment:9 Changed 7 years ago by 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?

comment:10 in reply to:  8 Changed 7 years ago by 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.

comment:11 in reply to:  9 Changed 7 years ago by 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.

comment:12 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from ryandesign to michaelld

comment:13 Changed 7 months ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added
Note: See TracTickets for help on using tickets.