From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: Ola x Nilsson <Ola.x.Nilsson@axis.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] v2: Y2038: Sanity checker for non-64-bit time and file functions
Date: Fri, 16 Dec 2022 12:47:50 +0100 [thread overview]
Message-ID: <jwqwn6ra7ri.fsf@axis.com> (raw)
In-Reply-To: <20221216114650.854563-1-olani@axis.com>
On Fri, Dec 16 2022, Ola x Nilsson wrote:
> v2:
>
> Renamed conf/distro/time64.conf -> conf/distro/time64.inc
> Use SITEINFO_BITS to select when to apply GLIBC_64BIT_TIME_FLAGS.
>
>
> I did not add _LARGEFILE to the option yet as I do not believe it is
> the right place.
> The _TIME_BITS=64 and _FILE_OFFSET_BITS=64 option redefine types and
> functions. The _LARGEFILE* options add new types and functions. The
> purpose of the time64.inc file is to enforce the redefinition of
> time_t and other types in code that has not bothered before. The
> _LARGEFILE* options should probably only be used by code that has
> explicitly chosen to use these glibc extensions, possible configured
> by autoconf.
I'm working on time64 support in pulseaudio at the moment. If anyone
else has started on pulseaudio I can move on to something else.
--
Ola x Nilsson
prev parent reply other threads:[~2022-12-16 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 11:46 v2: Y2038: Sanity checker for non-64-bit time and file functions Ola x Nilsson
2022-12-16 11:46 ` [PATCH RFC v2 1/2] Add QA check for 32 bit time and file offset functions Ola x Nilsson
2022-12-16 11:46 ` [PATCH RFC v2 2/2] time64.inc: Include to enable 64 bit time flags Ola x Nilsson
2022-12-16 11:47 ` Ola x Nilsson [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=jwqwn6ra7ri.fsf@axis.com \
--to=ola.x.nilsson@axis.com \
--cc=openembedded-core@lists.openembedded.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