Summary: | dev-python/graph-tool-2.2.44 with dev-libs/boost-1.62.0-r1 - graph_hits.cc:71:44: error: reference to ‘placeholders’ is ambiguous | ||||||
---|---|---|---|---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris White <cwprogram> | ||||
Component: | Stabilization | Assignee: | Python Gentoo Team <python> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | normal | CC: | joost.ruis, pacho | ||||
Priority: | Normal | Keywords: | STABLEREQ | ||||
Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Package list: |
=dev-python/graph-tool-2.19
|
Runtime testing required: | No | ||||
Bug Depends on: | 601624 | ||||||
Bug Blocks: | 590244 | ||||||
Attachments: |
|
Running: append-cxxflags -std=c++14 (from flag-o-matic.eclass) could help to get it fixed with older gcc versions :/ Did you try? also try with 2.19 Just for the record. 2.19 fails to configure. checking whether x86_64-pc-linux-gnu-g++ supports C++14 features by default... no checking whether x86_64-pc-linux-gnu-g++ supports C++14 features with -std=gnu++14... no checking whether x86_64-pc-linux-gnu-g++ supports C++14 features with -std=gnu++0x... no configure: error: *** A compiler with support for C++14 language features is required. my gcc-config: x86_64-pc-linux-gnu-4.9.3-vanilla * graph-tool-2.19 needs GCC 5 at least. Until GCC 5 is not stabilised, we can't fix this. I'm experiencing this also. Why did Gentoo drop the older boost ebuilds, they worked fine and now I've got 5 bugs that I can't fix or work around? 2.19 is stabilised now. commit d848f64957066a30a8429ced59354f00f15b5620 Author: David Seifert <soap@gentoo.org> Date: Wed May 17 20:05:50 2017 +0200 dev-python/graph-tool: Remove old Bug: https://bugs.gentoo.org/show_bug.cgi?id=601036 |
Created attachment 454566 [details] build.log Attached is a build log. I attempted seeing if the unstable graph-tool-2.16 might work but it requires C++14 support not available in stable gcc and there's also #596950. The only other solution there might be is to update to the latest graph-tool (2.19) and see if it fixes the issue.