From bbc8cc1cb6ed0db859bc6caf6b52d8913d51506e Mon Sep 17 00:00:00 2001 From: Waldemar Brodkorb Date: Sat, 13 Jul 2024 11:33:18 +0200 Subject: [PATCH] docs: add time64 status of uClibc-ng Signed-off-by: Waldemar Brodkorb Signed-off-by: Thomas Petazzoni --- docs/manual/faq-troubleshooting.adoc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/manual/faq-troubleshooting.adoc b/docs/manual/faq-troubleshooting.adoc index 5f132f99f6..2122a6892f 100644 --- a/docs/manual/faq-troubleshooting.adoc +++ b/docs/manual/faq-troubleshooting.adoc @@ -253,9 +253,10 @@ There are multiple situations to consider: * On 32-bit architectures, the situation depends on the C library: - ** With _uclibc-ng_, there is no support for 64-bit +time_t+ on - 32-bit architectures, so systems using _uclibc-ng_ on 32-bit - platforms will not be Y2038 compatible. + ** With _uclibc-ng_, there is support for 64-bit +time_t+ on 32-bit + architectures since version 1.0.46, so systems using _uclibc-ng_ + on 32-bit platforms will be Y2038 compatible when + UCLIBC_USE_TIME64 is y. This is the default since 1.0.49. ** With _musl_, 64-bit +time_t+ has always been used on 32-bit architectures, so systems using _musl_ on 32-bit platforms are