From 1185c0256bb43bd451e73249d53915db42409476 Mon Sep 17 00:00:00 2001 From: James Hilliard Date: Sun, 26 Nov 2023 13:33:41 -0700 Subject: [PATCH] package/python-msgpack: fix build without cpp toolchain Prior to being updated to version 1.0.7 in 014a66fcde68bd0b612b62ec722ccc93bdc0d7f9 python-msgpack would automatically fall back to the pure python version if the cpp based optimized extension would fail to build for any reason. This however is no longer the case after updating to 1.0.7 where it is now required that we explicitely set the MSGPACK_PUREPYTHON=1 if we do not have cpp support enabled in the toolchain. Fixes: - http://autobuild.buildroot.net/results/361/36185a19bed4bd57421a4d909bce1976c89d130f - http://autobuild.buildroot.net/results/477/477f822cb196ebc2246bcbdc1b6eaf940fc018cd Signed-off-by: James Hilliard [yann.morin.1998@free.fr: add the comment] Signed-off-by: Yann E. MORIN --- package/python-msgpack/python-msgpack.mk | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/package/python-msgpack/python-msgpack.mk b/package/python-msgpack/python-msgpack.mk index 061ff5a761..3ee7c54ce1 100644 --- a/package/python-msgpack/python-msgpack.mk +++ b/package/python-msgpack/python-msgpack.mk @@ -11,4 +11,11 @@ PYTHON_MSGPACK_LICENSE = Apache-2.0 PYTHON_MSGPACK_LICENSE_FILES = COPYING PYTHON_MSGPACK_SETUP_TYPE = setuptools +# When set in the environment, whatever the value, MSGPACK_PUREPYTHON drives +# using the pure python implementation rather than rely on the C++ native code. +# So we can't force it to use C++; we can only force it to use pure python. +ifeq ($(BR2_INSTALL_LIBSTDCPP),) +PYTHON_MSGPACK_ENV = MSGPACK_PUREPYTHON=1 +endif + $(eval $(python-package))