All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/unscd: disable on riscv32
Date: Thu, 27 May 2021 22:19:04 +0200	[thread overview]
Message-ID: <20210527201904.478811-1-fontaine.fabrice@gmail.com> (raw)

unscd unconditionally uses __NR_clock_gettime which will raise the
following build failure on riscv32:

nscd-0.54.c:339:14: error: '__NR_clock_gettime' undeclared (first use in this function); did you mean 'clock_gettime'?
  339 |  if (syscall(__NR_clock_gettime, CLOCK_MONOTONIC, &ts))
      |              ^~~~~~~~~~~~~~~~~~
      |              clock_gettime

Fixes:
 - http://autobuild.buildroot.org/results/eb77b18f268d8e59c407f757662117a33d3f9ee3

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
 package/unscd/Config.in | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/unscd/Config.in b/package/unscd/Config.in
index 23cc5a4fcb..88f1062103 100644
--- a/package/unscd/Config.in
+++ b/package/unscd/Config.in
@@ -1,5 +1,6 @@
 config BR2_PACKAGE_UNSCD
 	bool "unscd"
+	depends on !BR2_RISCV_32
 	depends on BR2_TOOLCHAIN_USES_GLIBC
 	help
 	  Micro Name Service Caching Daemon
@@ -22,4 +23,5 @@ config BR2_PACKAGE_UNSCD
 	  http://busybox.net/~vda/unscd
 
 comment "unscd needs a glibc toolchain"
+	depends on !BR2_RISCV_32
 	depends on !BR2_TOOLCHAIN_USES_GLIBC
-- 
2.30.2

             reply	other threads:[~2021-05-27 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 20:19 Fabrice Fontaine [this message]
2021-06-01 20:35 ` [Buildroot] [PATCH 1/1] package/unscd: disable on riscv32 Arnout Vandecappelle
2021-06-10  8:44 ` Peter Korsgaard

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=20210527201904.478811-1-fontaine.fabrice@gmail.com \
    --to=fontaine.fabrice@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.