All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH RFC 3/3] time64.conf: Include to enable 64 bit time flags
Date: Fri, 9 Dec 2022 11:36:03 +0100	[thread overview]
Message-ID: <jwqwn70c168.fsf@axis.com> (raw)
In-Reply-To: <CANNYZj_NFOejE6Xe2xHTTWkuMVY2TmPGpXTZYT=3+5V1Y2u3Xg@mail.gmail.com>


On Thu, Dec 08 2022, Alexander Kanavin wrote:

> On Thu, 8 Dec 2022 at 08:11, Ola x Nilsson <olani@axis.com> wrote:
>> +GLIBC_64BIT_TIME_FLAGS:pn-glibc = ""
>> +GLIBC_64BIT_TIME_FLAGS:pn-glibc-tests = ""
>> +# pipewire-v4l2 explicitly sets _FILE_OFFSET_BITS=32 to get access to
>> +# both 32 and 64 bit file APIs.  But it does not handle the time side?
>> +# Needs further investigation
>> +GLIBC_64BIT_TIME_FLAGS:pn-pipewire = ""
>> +GLIBC_64BIT_TIME_FLAGS:pn-gcc-sanitizers = ""
>> +
>> +INSANE_SKIP:libstd-rs[_usr_lib_rustlib_armv7-poky-linux-gnueabihf_lib_libstd.so]
>> = "clock_gettime gettime fcntl fstat64 fstatat64 getsockopt ioctl
>> lstat64 nanosleep prctl recvmsg sendmsg setsockopt stat64"
>> +INSANE_SKIP:librsvg[_usr_bin_rsvg-convert] = "fcntl fstat64 prctl stat64 clock_gettime"
>> +INSANE_SKIP:librsvg[_usr_lib_librsvg-2.so.2.48.0] = "fcntl lstat64
>> setsockopt sendmsg fstat64 getsockopt ioctl nanosleep timegm
>> fstatat64 prctl mktime gmtime_r recvmsg stat64 clock_gettime
>> localtime_r"
>> +
>> +# libpulsedsp.so is a preload-library that hooks libc functions
>> +INSANE_SKIP:pulseaudio[_usr_lib_pulseaudio_libpulsedsp.so] = "setsockopt fcntl"
>
> Some of these perhaps need a ticket in bugzilla, and there should be a
> meta-ticket for Y2038 that tracks individual issues (by depending on
> them). Can you arrange that please?

I can file tickets if that's the way we want to go.  I'm not really at
that point yet, these are just for the packages that were included in
our products.  I've just done one plain poky build to make sure this
stuff worked so far.

-- 
Ola x Nilsson


  parent reply	other threads:[~2022-12-09 10:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  7:11 Y2038: Sanity checker for non-64-bit time and file functions Ola x Nilsson
2022-12-08  7:11 ` [PATCH RFC 1/3] glibc: Add ppoll fortify symbol for 64 bit time_t Ola x Nilsson
2022-12-08  7:11 ` [PATCH RFC 2/3] Add QA check for 32 bit time and file offset functions Ola x Nilsson
2022-12-17 11:17   ` [OE-core] " Richard Purdie
2022-12-17 17:19     ` Khem Raj
2022-12-08  7:11 ` [PATCH RFC 3/3] time64.conf: Include to enable 64 bit time flags Ola x Nilsson
2022-12-08 10:00   ` [OE-core] " Alexander Kanavin
2022-12-08 10:10     ` Richard Purdie
2022-12-09 10:31       ` Ola x Nilsson
2022-12-09 10:36     ` Ola x Nilsson [this message]
2022-12-09 13:06       ` Alexandre Belloni
2022-12-09  0:23   ` Khem Raj
2022-12-09  9:55     ` Ola x Nilsson
2022-12-09 12:35       ` Richard Purdie
2022-12-09 13:09       ` Alexandre Belloni
2022-12-09 13:13         ` Alexander Kanavin
2022-12-09 13:29           ` Richard Purdie
2022-12-09 16:36         ` Khem Raj
2022-12-09 16:47       ` Khem Raj
2022-12-15 16:32   ` Khem Raj
2022-12-17 11:15     ` Richard Purdie
2022-12-16 18:44   ` Khem Raj

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=jwqwn70c168.fsf@axis.com \
    --to=ola.x.nilsson@axis.com \
    --cc=alex.kanavin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.