python: prevent build failure when pycache files missing
PATCH 1/1 python: prevent build failure when pycache files missing
Building a patched version of python3 with byte-code files saved to their legacy locations and names causes the following errors:
| rm: cannot remove '/.../build/tmp/work/x86_64-linux/python3-native/3.9.9-r0/recipe-sysroot-native/usr/lib/python3.9/test/__pycache__/test_range.cpython*': No such file or directory | rm: cannot remove '/.../build/tmp/work/x86_64-linux/meson-native/0.57.1-r1/recipe-sysroot-native/usr/lib/python*/site-packages/mesonbuild/dependencies/__pycache__/mpi.cpython*': No such file or directory
Force remove pycache files, preventing build failure in case they are absent.
Python3 patched with legacy byte-code locations in order to create a sourceless .pyc deployment for small flash boxes. Unappropriate for upstream.
--- meta/recipes-devtools/meson/meson.inc | 2 +- meta/recipes-devtools/python/python3_3.9.9.bb | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-devtools/meson/meson.inc +1 -1
@@ -44,5 +44,5 @@ do_install_append () { # Upstream is discussing ways to solve the issue properly, until then let's # just not install the problematic files. # More info: http://benno.id.au/blog/2013/01/15/python-determinism - rm ${D}${libdir}/python*/site-packages/mesonbuild/dependencies/__pycache__/mpi.cpython* + rm -f ${D}${libdir}/python*/site-packages/mesonbuild/dependencies/__pycache__/mpi.cpython* }
meta/recipes-devtools/python/python3_3.9.9.bb +2 -2
@@ -174,8 +174,8 @@ do_install_append() { # Upstream is discussing ways to solve the issue properly, until then let's # just not install the problematic files. # More info: http://benno.id.au/blog/2013/01/15/python-determinism - rm ${D}${libdir}/python${PYTHON_MAJMIN}/test/__pycache__/test_range.cpython* - rm ${D}${libdir}/python${PYTHON_MAJMIN}/test/__pycache__/test_xml_etree.cpython* + rm -f ${D}${libdir}/python${PYTHON_MAJMIN}/test/__pycache__/test_range.cpython* + rm -f ${D}${libdir}/python${PYTHON_MAJMIN}/test/__pycache__/test_xml_etree.cpython* } do_install_append_class-nativesdk () {
Signature · 1 line
2.20.1
Quoted 12 lines · Athanasios Oikonomou
Building a patched version of python3 with byte-code files saved to their legacy locations and names causes the following errors:
Quoted 8 lines
rm: cannot remove '/.../build/tmp/work/x86_64-linux/python3-native/3.9.9- r0/recipe-sysroot- native/usr/lib/python3.9/test/__pycache__/test_range.cpython*': No such file or directory
rm: cannot remove '/.../build/tmp/work/x86_64-linux/meson-native/0.57.1- r1/recipe-sysroot-native/usr/lib/python*/site- packages/mesonbuild/dependencies/__pycache__/mpi.cpython*': No such file or directory
Quoted 4 lines
Force remove pycache files, preventing build failure in case they are absent.
Python3 patched with legacy byte-code locations in order to create a sourceless .pyc deployment for small flash boxes. Unappropriate for upstream.
Do people commonly patch python to build with legacy byte-code locations? If you do that aren't files generated at a different location and hence break reproduciblity? This seems to be a rather niche requirement?
I'm a little worried we add the -f and then if files change location, we don't realise...
Cheers,
Richard