Skip to content

6.1: build with 64-bit time_t on 32-bit platforms #5228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: release/6.1
Choose a base branch
from

Conversation

lhoward
Copy link
Contributor

@lhoward lhoward commented Jun 28, 2025

  • Explanation: It is good practice to build with 64-bit time_t/timeval on 32-bit platforms to avoid the Y2038 issue. This is the default when building on Yocto for armv7, for example. Unfortunately suseconds_t is not an alias to a type of the correct width (unlike time_t), so for Glibc make it a private alias of time_t to fix the build.
  • Scope: Linux build fix
  • Issues:
  • Original PRs: build with 64-bit time_t on 32-bit platforms #5231
  • Risk: minimum
  • Testing:
  • Reviewers:

It is good practice to build with 64-bit time_t/timeval on 32-bit platforms to
avoid the Y2038 issue. This is the default when building on Yocto for armv7,
for example. Unfortunately suseconds_t is not an alias to a type of the correct
width (unlike time_t), so for Glibc make it a private alias of time_t to fix
the build.
@lhoward
Copy link
Contributor Author

lhoward commented Jun 28, 2025

If for process reasons you need a PR against main, can do, just lmk once this is reviewed. Sorry to do it back to front.

@lhoward lhoward changed the title build with 64-bit time_t on 32-bit platforms 6.1: build with 64-bit time_t on 32-bit platforms Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant