From: Lukasz Majewski <lukma@denx.de>
To: Adhemerval Zanella via Libc-help <libc-help@sourceware.org>,
Jacob Avraham <jacob.avraham@auto-talks.com>
Subject: Re: support to y2038 for ARM 32b architecture
Date: Tue, 7 Dec 2021 14:42:00 +0100 [thread overview]
Message-ID: <20211207144200.045b13c8@ktm> (raw)
In-Reply-To: <8e18d86f-ad11-e94e-43d9-73251b4f38da@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
Hi,
> On 05/12/2021 12:39, Jacob Avraham via Libc-help wrote:
> > Hi,
> > Does the latest glibc version support y2038 for ARM 32bit
> > architecture and if not, when is it planned for?
> >
> > Thanks,
> > Jacob Avraham
> >
>
> Yes, since GLIBC 2.34. From NEWS file:
>
> * Add support for 64-bit time_t on configurations like x86 where
> time_t is traditionally 32-bit. Although time_t still defaults to
> 32-bit on these configurations, this default may change in future
> versions. This is enabled with the _TIME_BITS preprocessor macro set
> to 64 and is only supported when LFS (_FILE_OFFSET_BITS=64) is also
> enabled. It is only enabled for Linux and the full support requires
> a minimum kernel version of 5.1.
This meta layer can help with integration:
https://github.com/lmajewski/meta-y2038
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-12-07 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 15:39 Jacob Avraham
2021-12-07 12:48 ` Adhemerval Zanella
2021-12-07 13:42 ` Lukasz Majewski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211207144200.045b13c8@ktm \
--to=lukma@denx.de \
--cc=jacob.avraham@auto-talks.com \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).