| Summary: | dev-util/cmake detects the wrong version of libboost_python outside of portage | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Christoph Junghans (RETIRED) <junghans> |
| Component: | [OLD] Development | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | Inclusion, PATCH |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | http://www.cmake.org/Bug/view.php?id=12955 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | patch against gx86 version | ||
Thanks, this is now in the KDE overlay for testing. Thanks for reporting. This is fixed in cvs now. Please sync. + + 06 May 2014; Johannes Huber <johu@gentoo.org> +cmake-2.8.12.2-r1.ebuild, + +files/cmake-2.8.12.2-FindBoost-python.patch: + Revision bump adds patch to find the correct version libboost_python outside + of portage by Christoph Junghans <ottxor@gentoo.org>, bug #500442. + |
Created attachment 369664 [details, diff] patch against gx86 version Outside of portage, in the case the default python interpreter is python3, but python2 is requested by find_package(PythonInterp 2), cmake will detect the wrong libboost_python, namely libboost_python-3.X.so. This issue is gentoo specific as we name libboost_python in a non-standard way. The attached patch improves the situation a bit, as one can assume that PYTHON_EXECUTABLE is set to the right interpreter by cmake.