From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Vincent Cruz <mooz@blockos.org>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/sysrepo: fix build on riscv32
Date: Fri, 5 Jun 2026 14:49:16 +0200 [thread overview]
Message-ID: <20260605124916.270695-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260218124726.120001-1-mooz@blockos.org>
In reply of:
> 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>
Applied to 2026.02.x. Thanks
> ---
> 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
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-06-05 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 12:46 [Buildroot] [PATCH] package/sysrepo: fix build on riscv32 Vincent Cruz
2026-02-24 6:17 ` Vincent Jardin via buildroot
2026-02-24 14:23 ` Thomas Petazzoni via buildroot
2026-02-27 9:54 ` Vincent Cruz
2026-02-27 13:11 ` Thomas Petazzoni via buildroot
2026-02-27 14:33 ` Vincent Cruz
2026-05-31 17:07 ` Thomas Petazzoni via buildroot
2026-06-05 12:49 ` Thomas Perale via buildroot [this message]
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=20260605124916.270695-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=mooz@blockos.org \
--cc=thomas.perale@mind.be \
/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