Summary: | >=dev-libs/boost-1.61.0-r1 : error: Name clash for '<pstage/lib>libboost_system.so.1.61.0' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | David Seifert <soap> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | cpp+disabled, deference, herrtimson, office, plevine457, yamadharma |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-libs:boost-1.61.0-r1:20160921-115618.log
emerge-history.txt environment emerge --info |
Description
Toralf Förster
![]() Created attachment 447172 [details]
dev-libs:boost-1.61.0-r1:20160921-115618.log
Created attachment 447174 [details]
emerge-history.txt
Created attachment 447176 [details]
environment
*** Bug 594702 has been marked as a duplicate of this bug. *** Maybe related to https://svn.boost.org/trac/boost/ticket/10858 I have two systems bowth of which are affected by this bug. This bug also affects boost-1.63.0 . (In reply to Andreas K. Hüttel from comment #5) > Maybe related to https://svn.boost.org/trac/boost/ticket/10858 That bug is related to different inconsistent implicit build flags (address-model=64 architecture=x86). Note the important part of this bug is: > error: Tried to build the target twice, with property sets having > error: these incompatible properties: > error: > error: - <threading>single > error: - <threading>multi > error: > error: Please make sure to have consistent requirements for these > error: properties everywhere in your project, especially for install > error: targets. This appears to be caused by 'threading=multi' implicitly being added to the explicit build option 'threading=single' I can't reproduce this bug. The posted log file shows that 'threading=single' was passed to the command line, but current Gentoo ebuilds only allow for 'threading=multi', supposedly because of a different bug. i.e., from boost-1.63.0.ebuild: > # building with threading=single is currently not possible > # https://svn.boost.org/trac/boost/ticket/7105 > threading=multi (In reply to deference from comment #6) > I have two systems bowth of which are affected by this bug. > This bug also affects boost-1.63.0 . Given that this bug seems to be triggered by the'threading=single' which is omitted in current ebuilds, yours is likely triggered by some other build flag misconfiguration. If so, you might want to post the full error message as a different bug. (In reply to deference from comment #6) > I have two systems bowth of which are affected by this bug. > This bug also affects boost-1.63.0 . Could you please add your emerge --info output here? I may be hanging myself out of a window here, but this does not look gcc-6 related to me, more some oddity with boost build system. Created attachment 500468 [details]
emerge --info
Sorry for the delay, I forgot about this bug and then I wanted to confirm what USE flag made it build and if this bug was still present.
It is but the USE flag can change based on the system, for my laptop (attached is it's emerge --info), it is static-libs, for my desktop it is tools.
I can tell you don't know what is causing this so just my 2 cents, it looks like this might be a race condition where something gets updated too soon or too late.
Thanks!
Please retest with masked 1.70.0, and file a new bug if the problem persists. |