Summary: | dev-libs/boost-1.65 - b2: error: Name clash for '<p../dist/bin>auto_index' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | roger |
Component: | Current packages | Assignee: | David Seifert <soap> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | jstein, office |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log.xz |
Description
roger
2019-06-10 23:52:49 UTC
In your toolchain you keep alive a masked: sys-devel/binutils: 2.30-r4::gentoo If you don't know anything about it, then try to clean your toolchain. Perhaps a simple "emerge --depclean" will do it for you. Since all your boost libs were compiled but didn't link, I came to this conclusion. (In reply to Ulenrich from comment #1) > In your toolchain you keep alive a masked: > sys-devel/binutils: 2.30-r4::gentoo > > If you don't know anything about it, > then try to clean your toolchain. Perhaps a > simple "emerge --depclean" will do it for you. > Since all your boost libs were compiled but didn't > link, I came to this conclusion. Thank you for your reply. I did attempt a 'emerge --depclean' before submitting my bug. Unfortunately it won't work since the boost libs are being pulled in as a dependency for another lib. Also 'emerge --update --newuse --deep --with-bdeps=y @world' won't run, as the boost libs are the first package it tries to rebuild. I see the same failure when I have the tools and static-libs use flag on for boost. Fixed by turning off tools. Not sure if this is something upstream or not. Disabling the static flags was how I overcame the issue. |