Bug 13606 - is it 2038 problem?
Summary: is it 2038 problem?
Status: RESOLVED INVALID
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.33.x
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-10 16:48 UTC by vyaceslav
Modified: 2021-06-04 18:32 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
log (23.91 KB, text/x-log)
2021-03-10 16:48 UTC, vyaceslav 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vyaceslav 2021-03-10 16:48:43 UTC 
Created attachment 8786 [details]
log

hello

I built the system with last buldroot 2021.02

Toolchain is linaro
http://snapshots.linaro.org/components/toolchain/binaries/10.2-2021.01-3/arm-linux-gnueabihf/
that has glibc 2.32 and linux headers 5.10

now the problem:
with date and hwclock cannot set time after 2038.

see attached file
Comment 1 Denys Vlasenko 2021-06-04 18:32:26 UTC 
Yes, time_t type is signed 32-bit on this arch.