From 5ad4ac083276b3504889c39351a56d947f172b5f Mon Sep 17 00:00:00 2001 From: Thomas Petazzoni Date: Thu, 13 Nov 2014 22:23:23 +0100 Subject: [PATCH] python3: don't use wcsftime() on uClibc As investigated in bug #7646, wcsftime() doesn't work properly with uClibc. Until it gets fixed in uClibc, let's tell Python 3 to not use it. Python 3 will fall back to strftime(), which works properly. [Peter: fix typo in comment] Signed-off-by: Thomas Petazzoni Cc: Beyonlo Signed-off-by: Peter Korsgaard --- package/python3/python3.mk | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/package/python3/python3.mk b/package/python3/python3.mk index 2c1ef2a56..5c72c6ebc 100644 --- a/package/python3/python3.mk +++ b/package/python3/python3.mk @@ -107,6 +107,12 @@ PYTHON3_CONF_ENV += \ ac_cv_file__dev_ptc=yes \ ac_cv_working_tzset=yes +# uClibc is known to have a broken wcsftime() implementation, so tell +# Python 3 to fall back to strftime() instead. +ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y) +PYTHON3_CONF_ENV += ac_cv_func_wcsftime=no +endif + PYTHON3_CONF_OPTS += \ --without-ensurepip \ --without-cxx-main \