From 5a268f95a5bf5ee8c244a8af685d6c84aad9a4ac Mon Sep 17 00:00:00 2001 From: Zqiang Date: Tue, 3 Aug 2021 13:11:38 +0800 Subject: [PATCH] python3: use monotonic clock for condvar if possible The timeout for threading.Lock, threading.Condition, etc, is not using a monotonic clock, it is affected if the system time (realtime clock) is set. This patch will make condvar use monotonic clock. Refence: https://bugs.python.org/issue41710 Signed-off-by: Zqiang Signed-off-by: Richard Purdie --- meta/recipes-devtools/python/python3_3.9.6.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-devtools/python/python3_3.9.6.bb b/meta/recipes-devtools/python/python3_3.9.6.bb index 9fe8e03389..34500642d4 100644 --- a/meta/recipes-devtools/python/python3_3.9.6.bb +++ b/meta/recipes-devtools/python/python3_3.9.6.bb @@ -74,6 +74,9 @@ DEPENDS = "bzip2-replacement-native libffi bzip2 openssl sqlite3 zlib virtual/li DEPENDS:append:class-target = " python3-native" DEPENDS:append:class-nativesdk = " python3-native" +# force to use the mutex+cond implementation (https://bugs.python.org/issue41710) +CFLAGS += "-DHAVE_BROKEN_POSIX_SEMAPHORES" + EXTRA_OECONF = " --without-ensurepip --enable-shared --with-platlibdir=${baselib}" EXTRA_OECONF:append:class-native = " --bindir=${bindir}/${PN}" -- 2.40.1