Created attachment 536078 [details] sys-apps:paludis-9999:20180617-083133.log Not sure if it's paludis, our boost install or cmake modules. One thing that is certain, is that it used to work in March and stopped working recently. -- Found PythonInterp: /var/tmp/portage/sys-apps/paludis-9999/temp/python2.7/bin/python (found version "2.7.14") -- Found PythonLibs: /usr/lib64/libpython2.7.so (found version "2.7.14") CMake Error at /usr/share/cmake/Modules/FindBoost.cmake:2044 (message): Unable to find the requested Boost libraries. Boost version: 1.65.0 Boost include path: /usr/include Could not find the following Boost libraries: boost_python No Boost libraries were found. You may need to set BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT to the location of Boost. Call Stack (most recent call first): CMakeLists.txt:322 (find_package)
That is a "well-known" problem of CMake's finder... it has no way to specify what Python version you want to find for `boost_python` (a few years ago I proposed a patch, but it was refused...), moreover `boost::python` library itself may have different suffixes and they vary in Linux distributions. But it seems (I didn't check it yet) new boost >= 1.67 (don't recall exact version... maybe 1.66) would have an explicit naming policy for `boost::python` versions. Also, CMake's 3.12 `FindBoost` AFAIK has adopted this scheme already... So I hope this "problem" would disappear forever... But, I think `paludis` needs to be fixed anyway (I can do that, but dunno how to reach upstream) PS. I'm a paludis user > 10 years, and very *very* upset about your email :(
Fixed in 0902bec in https://github.com/MageSlayer/paludis-gentoo-patches
