public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Pőcze Barnabás" <pobrn@protonmail.com>
To: uvv.mail@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] time64: Use consistent TIME defines
Date: Tue, 20 Jan 2026 17:47:05 +0000	[thread overview]
Message-ID: <fb54cd99-7219-4a35-abd6-5044a5f11631@protonmail.com> (raw)
In-Reply-To: <20260120103834.1780598-1-uvv.mail@gmail.com>

Hi

2026. 01. 20. 11:38 keltezéssel, uvv.mail@gmail.com írta:
> From: Vyacheslav Yurkov <uvv.mail@gmail.com>
> 
> Pipewire crashes when other dependent libraries are built with the
> different TIME and FILE_OFFSET defines. pw-v4l2/libcamera will most

That is specifically about "libcameraify", which is a similar LD_PRELOAD
library. I wouldn't mention it since this change does not affect the
libcamera recipe.


> likely not work with 32-bits that have 64-bit time but that has to be
> fixed in the respective projects.

As the removed comment correctly points out, __ioctl_time64, etc. is not handled
in pw-v4l2. But I'm still not sure why the change was made originally in yocto since
it won't make pw-v4l2 somehow work if an application uses __ioctl_time64.

In any case, the current situation is less than ideal, if pipewire and its dependencies
(e.g. alsa-lib) disagree about the size of time_t, etc; as two people have already
reported issues caused by this.


Regards,
Barnabás Pőcze

> 
> Related bug report:
> https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5055
> 
> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
> Signed-off-by: Barnabás Pőcze <pobrn@protonmail.com>
> ---
>   meta/conf/distro/include/time64.inc | 4 ----
>   1 file changed, 4 deletions(-)
> 
> diff --git a/meta/conf/distro/include/time64.inc b/meta/conf/distro/include/time64.inc
> index 24a81c83f1..3ed0a4253d 100644
> --- a/meta/conf/distro/include/time64.inc
> +++ b/meta/conf/distro/include/time64.inc
> @@ -21,10 +21,6 @@ TARGET_CC_ARCH:append:x86 = "${@bb.utils.contains('TUNE_FEATURES', 'm32', '${GLI
> 
>   GLIBC_64BIT_TIME_FLAGS:pn-glibc = ""
>   GLIBC_64BIT_TIME_FLAGS:pn-glibc-testsuite = ""
> -# 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 = ""
>   # Undefines _FILE_OFFSET_BITS on purpose in
>   # libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp
>   GLIBC_64BIT_TIME_FLAGS:pn-gcc-sanitizers = ""




      reply	other threads:[~2026-01-20 19:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 10:38 [PATCH] time64: Use consistent TIME defines uvv.mail
2026-01-20 17:47 ` Pőcze Barnabás [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=fb54cd99-7219-4a35-abd6-5044a5f11631@protonmail.com \
    --to=pobrn@protonmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=uvv.mail@gmail.com \
    /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