diff options
author | Mark Asselstine <mark.asselstine@windriver.com> | 2016-03-17 12:25:05 -0400 |
---|---|---|
committer | Bruce Ashfield <bruce.ashfield@windriver.com> | 2016-03-21 10:26:01 -0400 |
commit | 5fcc6d24c35442dd1ac4018e1b2d2f981f0f20b2 (patch) | |
tree | 83e1480f2b2619c8d4b57e2737ae2d715157d5f8 /recipes-networking/openvswitch/openvswitch-git/kernel_module.patch | |
parent | f3e598729639546303e4bf041989417efe23613d (diff) | |
download | meta-virtualization-5fcc6d24c35442dd1ac4018e1b2d2f981f0f20b2.tar.gz |
lxc: fix build issue - unable to find Python.h
Prior to poky commit 3d45853eef1269b455d840a60491802251368378
[python3: fix do_configure check platform triplet error] lxc's
configure scripts would fail to find python3 and would therefor
configure with python3 support disabled.
After poky integrated the above commit lxc can, and does, detect
python3 and attempts to configure with python support. Unfortunately
it would detect the host's python3 which it would use to run setup.py
and therefor get the host's include path etc. and ultimately fail to
build.
To fix this we make 'python' support configurable via a PACKAGECONFIG
and we default to not configuring with this support, to match our
previous configuration. We also fix things such that 'python' support
can be enabled in the PACKAGECONFIG and the build will complete
successfully, using our python3 and not the host's.
We might want to eventually enable the python support but since this
not only enables python extensions but even goes as far as turning
scripts like lxc-ls into python scripts, instead of shell scripts,
keeping it disabled for now is the minimally invasive approach.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'recipes-networking/openvswitch/openvswitch-git/kernel_module.patch')
0 files changed, 0 insertions, 0 deletions