From: "prasanth" <ragaprasanth@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: raj.khem@gmail.com, Prasanth R <prasanth.r@lineo.co.jp>
Subject: [meta-multimedia][PATCH] libcamera: build with 64-bit time_t
Date: Fri, 16 Oct 2026 09:53:02 +0900 [thread overview]
Message-ID: <20261016005302.3710890-1-ragaprasanth@gmail.com> (raw)
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>
---
libcamera.so before:
recvmsg@GLIBC_2.4, ioctl@GLIBC_2.4, clock_gettime@GLIBC_2.17,
stat64@GLIBC_2.33, fstat64@GLIBC_2.33, sendmsg@GLIBC_2.4
after:
__recvmsg64, __ioctl_time64, __clock_gettime64,
__stat64_time64, __fstat64_time64, __sendmsg64 (GLIBC_2.34)
.../recipes-multimedia/libcamera/libcamera_0.7.2.bb | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/meta-multimedia/recipes-multimedia/libcamera/libcamera_0.7.2.bb b/meta-multimedia/recipes-multimedia/libcamera/libcamera_0.7.2.bb
index 955cf041ba..b468d2b9ed 100644
--- a/meta-multimedia/recipes-multimedia/libcamera/libcamera_0.7.2.bb
+++ b/meta-multimedia/recipes-multimedia/libcamera/libcamera_0.7.2.bb
@@ -94,10 +94,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"
--
2.34.1
reply other threads:[~2026-10-16 3:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261016005302.3710890-1-ragaprasanth@gmail.com \
--to=ragaprasanth@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=prasanth.r@lineo.co.jp \
--cc=raj.khem@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