Backport two patches to make it py3 friendly.
(From OE-Core rev: 647ff3bed1823b53a41a5c2640ffc5f4d50d1e11)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We previously patched configure to stop looking around for a Python to use, and
to use the Python binary and install paths that we specify. Now that we depend
on Python 3 its possible that bitbake is being built on a machine without Python
2 installed, so hardcode the python3 interpreter instead.
(From OE-Core rev: bb5a43f049c1a7cffb5516b1c3d0264dea68ea3f)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
xcb-proto had a dependency on python-native as it builds and installs a Python
module, but xcb-proto is very low in the build to force a dependency on
python-native.
As it turns out libxcb simply asks pkg-config for the full path to the module
xcb-proto installed and uses it directly so there is no need to build
python-native. Instead replace AM_PATH_PYTHON with two explicit variable
definitions (need to set PYTHON for automake's install logic).
Also remove the dependency on xcb-proto-native as libxcb uses the data files and
tooling from the target sysroot, and patching it to use the native sysroot adds
complication for no good reason.
(From OE-Core rev: bc38ef47b05128623a916172c2cfd244510b201e)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang
Ross Burton