meta-virtualization.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: meta-virtualization@lists.yoctoproject.org
Cc: Martin Jansa <Martin.Jansa@gmail.com>
Subject: [master-next][PATCH] virtiofsd: add seccomp to REQUIRED_DISTRO_FEATURES
Date: Fri,  1 Sep 2023 21:01:01 +0200	[thread overview]
Message-ID: <20230901190101.3898929-1-Martin.Jansa@gmail.com> (raw)

* otherwise causes world build failures for DISTROs without seccomp:

  ERROR: Nothing PROVIDES 'libseccomp' (but meta-virtualization/recipes-extended/virtiofsd/virtiofsd_1.7.0.bb DEPENDS on or otherwise requires it)
  libseccomp was skipped: missing required distro feature 'seccomp' (not in DISTRO_FEATURES)

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 recipes-extended/virtiofsd/virtiofsd_1.7.0.bb | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/recipes-extended/virtiofsd/virtiofsd_1.7.0.bb b/recipes-extended/virtiofsd/virtiofsd_1.7.0.bb
index 7224888..b8a9382 100644
--- a/recipes-extended/virtiofsd/virtiofsd_1.7.0.bb
+++ b/recipes-extended/virtiofsd/virtiofsd_1.7.0.bb
@@ -6,8 +6,11 @@ LIC_FILES_CHKSUM = " \
     file://LICENSE-APACHE;md5=3b83ef96387f14655fc854ddc3c6bd57 \
     file://LICENSE-BSD-3-Clause;md5=b1ed361f9fc790c1054d81a7ef041a34 \
 "
-DEPENDS += "libseccomp"
-DEPENDS += "libcap-ng"
+
+DEPENDS = "libseccomp libcap-ng"
+
+inherit features_check
+REQUIRED_DISTRO_FEATURES = "seccomp"
 
 SRC_URI += "crate://crates.io/virtiofsd/1.7.0"
 SRC_URI[virtiofsd-1.7.0.sha256sum] = "6f043afa23aedbb18f36084b9df831796a9e4c62e73a16fe557de0cf30d7708d"
-- 
2.42.0



             reply	other threads:[~2023-09-01 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 19:01 Martin Jansa [this message]
2023-09-04  3:06 ` [meta-virtualization] [master-next][PATCH] virtiofsd: add seccomp to REQUIRED_DISTRO_FEATURES Bruce Ashfield

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=20230901190101.3898929-1-Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=meta-virtualization@lists.yoctoproject.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).