* [PATCH v2] time64: Use consistent TIME defines
@ 2026-01-21 15:26 uvv.mail
0 siblings, 0 replies; only message in thread
From: uvv.mail @ 2026-01-21 15:26 UTC (permalink / raw)
To: openembedded-core; +Cc: Vyacheslav Yurkov, Barnabás Pőcze
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
Pipewire crashes when other dependent libraries are built with the
different TIME and FILE_OFFSET defines.
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 = ""
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2026-01-21 15:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-21 15:26 [PATCH v2] time64: Use consistent TIME defines uvv.mail
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox