|
@@ -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
|