libcamera: build with 64-bit time_t

64-bit time was turned off for all of libcamera because v4l2-compat.
libcamera fixed this upstream in v0.3.0 by also
undefining _TIME_BITS for v4l2-compat (commit 705601 "v4l2:
Unset _TIME_BITS in addition to _FILE_OFFSET_BITS"), so the
workaround is no longer needed.

v4l2-compat.so still uses 32-bit APIs on purpose, so keep the
32bit-time QA skip for it.

Signed-off-by: Prasanth R <prasanth.r@lineo.co.jp>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
This commit is contained in:
prasanth authored and Khem Raj committed 2026-10-15 22:32:06 -07:00
1 parent 56e7d0bd84
commit 0938f25dc9
1 file changed
+2 -4
@@ -95,10 +95,8 @@ FILES:${PN}-compliance = "${bindir}/lc-compliance"
FILES:${PN}-gst = "${libdir}/gstreamer-1.0"
FILES:${PN}-pycamera = "${PYTHON_SITEPACKAGES_DIR}/libcamera"
# libcamera-v4l2 explicitly sets _FILE_OFFSET_BITS=32 to get access to
# both 32 and 64 bit file APIs.
GLIBC_64BIT_TIME_FLAGS = ""
# v4l2-compat.so is built with 32-bit file and time APIs on purpose, so it
# can wrap both the 32 and 64-bit calls. The rest of libcamera uses 64-bit time.
INSANE_SKIP += "32bit-time"
CXXFLAGS += "-Wno-error=array-bounds"