On Sat, 2022-01-22 at 19:15 +0200, Athanasios Oikonomou wrote: > 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.
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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#160918): https://lists.openembedded.org/g/openembedded-core/message/160918 Mute This Topic: https://lists.openembedded.org/mt/88608680/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
