From: uvv.mail@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: "Vyacheslav Yurkov" <uvv.mail@gmail.com>,
"Barnabás Pőcze" <pobrn@protonmail.com>
Subject: [PATCH] time64: Use consistent TIME defines
Date: Tue, 20 Jan 2026 10:38:34 +0000 [thread overview]
Message-ID: <20260120103834.1780598-1-uvv.mail@gmail.com> (raw)
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
likely not work with 32-bits that have 64-bit time but that has to be
fixed in the respective projects.
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 = ""
next reply other threads:[~2026-01-20 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 10:38 uvv.mail [this message]
2026-01-20 17:47 ` [PATCH] time64: Use consistent TIME defines Pőcze Barnabás
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=20260120103834.1780598-1-uvv.mail@gmail.com \
--to=uvv.mail@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pobrn@protonmail.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