mirror of
https://git.yoctoproject.org/poky
synced 2026-05-08 17:19:20 +00:00
qemu: Ensure pip and the python venv aren't used for meson
Qemu wants to use a supported python version and a specific meson version to "help" users and uses pip and creates a venv to do this. This is a nightmare for us. Our versions stay up to date and should be supported so we don't really need/want this wrapping. Tweak things to disable it. There was breakage from the wrapper shown by: bitbake qemu-system-native <add DISTRO_FEATURES:remove = "opengl" to local.conf> bitbake qemu-system-native -c configure which would crash. The issue is the change in configuration removes pieces from the sysroot but pyc files remainm as do pieces of pip which causes problems. (From OE-Core rev: aceef7785e637a0223ecf288e2f367b6bee4a505) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
@@ -34,6 +34,7 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \
|
||||
file://fixedmeson.patch \
|
||||
file://fixmips.patch \
|
||||
file://0001-vfio-Include-libgen.h-for-basename-API.patch \
|
||||
file://no-pip.patch \
|
||||
file://qemu-guest-agent.init \
|
||||
file://qemu-guest-agent.udev \
|
||||
"
|
||||
|
||||
@@ -0,0 +1,45 @@
|
||||
qemu: Ensure pip and the python venv aren't used for meson
|
||||
|
||||
Qemu wants to use a supported python version and a specific meson version
|
||||
to "help" users and uses pip and creates a venv to do this. This is a nightmare
|
||||
for us. Our versions stay up to date and should be supported so we don't
|
||||
really need/want this wrapping. Tweak things to disable it.
|
||||
|
||||
There was breakage from the wrapper shown by:
|
||||
|
||||
bitbake qemu-system-native
|
||||
<add DISTRO_FEATURES:remove = "opengl" to local.conf>
|
||||
bitbake qemu-system-native -c configure
|
||||
|
||||
which would crash. The issue is the change in configuration removes pieces
|
||||
from the sysroot but pyc files remainm as do pieces of pip which causes
|
||||
problems.
|
||||
|
||||
Ideally we'd convince upstream to allow some way to disable the venv on
|
||||
the understanding that if/when it breaks, we keep the pieces. The patch
|
||||
as it stands is a workaround.
|
||||
|
||||
Upstream-Status: Inappropriate [oe specific]
|
||||
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
||||
|
||||
diff --git a/configure b/configure
|
||||
index 133f4e3235..e4c144b4e2 100755
|
||||
--- a/configure
|
||||
+++ b/configure
|
||||
@@ -1009,7 +1009,7 @@ python="$(command -v "$python")"
|
||||
echo "python determined to be '$python'"
|
||||
echo "python version: $($python --version)"
|
||||
|
||||
-python="$($python -B "${source_path}/python/scripts/mkvenv.py" create pyvenv)"
|
||||
+python=python3
|
||||
if test "$?" -ne 0 ; then
|
||||
error_exit "python venv creation failed"
|
||||
fi
|
||||
@@ -1017,6 +1017,7 @@ fi
|
||||
# Suppress writing compiled files
|
||||
python="$python -B"
|
||||
mkvenv="$python ${source_path}/python/scripts/mkvenv.py"
|
||||
+mkvenv=true
|
||||
|
||||
mkvenv_flags=""
|
||||
if test "$download" = "enabled" ; then
|
||||
Reference in New Issue
Block a user