When I was building core master from source on Debian Bullseye arm64, I got: file core/workdir/UnpackedTarball/python3/LO_lib/_sysconfigdata__linux_aarch64-unknown-linux-gnu.py does not exist in the tarball This is because python's config.sub removed `-unknown` from the triple. The actual filename is `_sysconfigdata__linux_aarch64-linux-gnu.py` I workaround it by: diff --git a/external/python3/ExternalPackage_python3.mk b/external/python3/ExternalPackage_python3.mk index aa3d8d93d77d..9f49f0994d13 100644 --- a/external/python3/ExternalPackage_python3.mk +++ b/external/python3/ExternalPackage_python3.mk @@ -143,7 +143,7 @@ else # put -pc in its linux platform triplets, so filter that... ifneq ($(OS),WNT) $(eval $(call gb_ExternalPackage_add_files,python3,$(LIBO_BIN_FOLDER)/python-core-$(PYTHON_VERSION)/lib,\ - LO_lib/_sysconfigdata__$(python3_MACHDEP)_$(subst i686,i386,$(subst -pc,,$(HOST_PLATFORM))).py \ + LO_lib/_sysconfigdata__$(python3_MACHDEP)_$(subst i686,i386,$(subst -unknown,,$(subst -pc,,$(HOST_PLATFORM)))).py \ )) endif And I think it should be fixed in upstream. Thanks.
Has nothing to do with Base, the database component of LO.
Michael: since it concerns Python, thought you might be interested in this one.
Just for info, searching "unknown" in git history of this file, I found a patch I had done: commit 8aae3b37a6553d645bfc94855adbbd1859e07692 Author: Julien Nabet <serval2412@yahoo.fr> Date: Sat Jan 2 16:40:01 2021 +0100 Fix build error in Python3 for Raspberry pi4b /home/pi/lo/libreoffice/external/python3/ExternalPackage_python3.mk:48: *** file /home/pi/lo/libreoffice/workdir/UnpackedTarball/python3/LO_lib/_sysconfigdata__linux_armv7l-unknown-linux-gnueabihf.py does not exist in the tarball. Arrêt. Change-Id: If348c9f55883c1afcc37ff38e84361786bef1845 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/108595 Tested-by: Jenkins Reviewed-by: Julien Nabet <serval2412@yahoo.fr> See https://cgit.freedesktop.org/libreoffice/core/commit/?id=8aae3b37a6553d645bfc94855adbbd1859e07692 So "unknown" was already a pb for me. Let's put this one to NEW since we got a trace from build failure.