From: mooz@blockos.org
To: buildroot@buildroot.org
Cc: Vincent Cruz <mooz@blockos.org>, Vincent Jardin <vjardin@free.fr>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/sysrepo: fix build on riscv32
Date: Wed, 18 Feb 2026 12:31:02 +0000 (UTC) [thread overview]
Message-ID: <1702535088.10290909.1771417862953.JavaMail.zimbra@blockos.org> (raw)
In-Reply-To: <20260217160154.2037308-1-mooz@blockos.org>
Hello,
I realized that I should have sent this patch as a new one and not as a reply to an existing thread.
I also forgot to include the package developers.
I will re-submit this patch.
Sorry for the inconvenience.
Vincent Cruz
-----Message original-----
De: Vincent <mooz@blockos.org>
à: buildroot <buildroot@buildroot.org>
Cc: Vincent <mooz@blockos.org>; Vincent <vjardin@free.fr>
Envoyé: mardi 17 février 2026 17:03 CET
Sujet : [PATCH v2 1/1] package/sysrepo: fix build on riscv32
Fixes:
https://autobuild.buildroot.net/results/b0f/b0f30feeddad1a8d51ac87af8b7c56fd9a9b5ff6/build-end.log
Upstream: https://github.com/sysrepo/sysrepo/commit/a0661b7e6a7b2f784fe3222048066c31187c6f92
Signed-off-by: Vincent Jardin <vjardin@free.fr>
Signed-off-by: Vincent Cruz <mooz@blockos.org>
---
v1 -> v2:
- Backport upstream patch.
Tested with Buildroot gitlab CI:
https://gitlab.com/v_cz/buildroot/-/pipelines/2331736795
...-sr_cond_futex-only-if-SYS_futex-sys.patch | 33 +++++++++++++++++++
1 file changed, 33 insertions(+)
create mode 100644 package/sysrepo/0001-cmake-UPDATE-use-sr_cond_futex-only-if-SYS_futex-sys.patch
diff --git a/package/sysrepo/0001-cmake-UPDATE-use-sr_cond_futex-only-if-SYS_futex-sys.patch b/package/sysrepo/0001-cmake-UPDATE-use-sr_cond_futex-only-if-SYS_futex-sys.patch
new file mode 100644
index 0000000000..d1d2eac758
--- /dev/null
+++ b/package/sysrepo/0001-cmake-UPDATE-use-sr_cond_futex-only-if-SYS_futex-sys.patch
@@ -0,0 +1,33 @@
+From 6917e00fb6c99a97dacdae7040e5c4c53752b10f Mon Sep 17 00:00:00 2001
+From: Vincent Cruz <mooz@blockos.org>
+Date: Tue, 17 Feb 2026 14:14:06 +0100
+Subject: [PATCH 1/1] cmake UPDATE use sr_cond_futex only if SYS_futex syscall
+ is available
+
+Some architectures (for ex. riscv32) may not support SYS_futex system
+call, even though linux/futex.h include file is present.
+
+Upstream: https://github.com/sysrepo/sysrepo/commit/a0661b7e6a7b2f784fe3222048066c31187c6f92
+
+Signed-off-by: Vincent Cruz <mooz@blockos.org>
+---
+ CMakeLists.txt | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 9b36de44..e1b39c8c 100644
+--- a/CMakeLists.txt
++++ b/CMakeLists.txt
+@@ -163,7 +163,8 @@ set(NACM_SRMON_DATA_PERM "600" CACHE STRING "NACM modules ietf-netconf-acm and s
+ # sr_cond implementation
+ if(NOT SR_COND_IMPL)
+ check_include_file("linux/futex.h" HAS_FUTEX)
+- if(HAS_FUTEX)
++ check_symbol_exists(SYS_futex "sys/syscall.h" HAS_SYS_FUTEX)
++ if(HAS_FUTEX AND HAS_SYS_FUTEX)
+ set(SR_COND_IMPL "sr_cond_futex")
+ else()
+ set(SR_COND_IMPL "sr_cond_pthread")
+--
+2.51.0
+
--
2.51.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-18 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 17:54 [Buildroot] [PATCH v1 0/2] Add python-libyang and python-sysrepo packages Vincent Jardin via buildroot
2026-01-07 17:54 ` [Buildroot] [PATCH v1 1/2] package/python-libyang: new package Vincent Jardin via buildroot
2026-01-07 22:40 ` Thomas Petazzoni via buildroot
2026-01-07 17:54 ` [Buildroot] [PATCH v1 2/2] package/python-sysrepo: " Vincent Jardin via buildroot
2026-01-07 22:45 ` Thomas Petazzoni via buildroot
2026-01-18 21:31 ` [Buildroot] [PATCH v1 0/1] package/sysrepo: fix build on riscv32 Vincent Jardin via buildroot
2026-01-18 21:31 ` [Buildroot] [PATCH v1 1/1] " Vincent Jardin via buildroot
2026-01-18 21:51 ` Thomas Petazzoni via buildroot
2026-02-17 16:00 ` [Buildroot] [PATCH v2 " Vincent Cruz
2026-02-18 12:31 ` mooz [this message]
2026-01-18 21:51 ` [Buildroot] [PATCH v1 0/1] " Thomas Petazzoni via buildroot
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=1702535088.10290909.1771417862953.JavaMail.zimbra@blockos.org \
--to=mooz@blockos.org \
--cc=buildroot@buildroot.org \
--cc=vjardin@free.fr \
/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