]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
boost: adjust hard-coded path after python3 upgrade
authorLukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
Mon, 7 Dec 2015 07:36:50 +0000 (08:36 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 9 Dec 2015 08:47:29 +0000 (08:47 +0000)
commit0eefd38a13a6ecb35f26ed8cd16f0b36f2c5d652
tree6628a4763ebfb22d78cbde10f30ff6d1833646dc
parentc8e0ec2da9ad4ce1c103966906a85f68c15400dd
boost: adjust hard-coded path after python3 upgrade

When using `PACKAGECONFIG = "python"` in the boost recipe, `bitbake boost`
fails at do_compile with:

    ./boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory
    compilation terminated.

This issue is due to the recent version upgrade from python 3.4 to 3.5:

701ec1977ced1bb08461e6de98b4f63d21cba8a6 python3: Upgrade from 3.4.3 to 3.5

The boost.inc file modifies the boost build configuration with a path
containing the python3 major version, which is hard-coded in the boost.inc
file. Hence after the python3 update, the path points to the outdated
location and it needs to be updated to the new location.

This issue was unrevealed by an internal continuous integration system
for the meta-ros application layer. Further manual bisecting lead to the
critical commit 701ec1977ced1bb08461e6de98b4f63d21cba8a6.

Signed-off-by: Lukas Bulwahn <lukas.bulwahn@oss.bmw-carit.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/recipes-support/boost/boost.inc