Skip to contentSkip to conversation

time64: Use consistent TIME defines

PATCH New [email protected] 1 participant 1 message Jan 21

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 time64: Use consistent TIME defines

From: Vyacheslav Yurkov <[email protected]>

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

---
 meta/conf/distro/include/time64.inc | 4 ----
 1 file changed, 4 deletions(-)
meta/conf/distro/include/time64.inc +0 -4
index 24a81c83f1..3ed0a4253d 100644
@@ -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 = ""