All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Scott Ellis" <jumpnowtek@gmail.com>
To: yocto@lists.yoctoproject.org
Cc: Scott Ellis <scott@jumpnowtek.com>
Subject: [yocto][PATCH] openssl: Fix dependency loop with PACKAGECONFIG cryptodev-linux
Date: Thu, 30 Apr 2020 20:23:11 +0000	[thread overview]
Message-ID: <20200430202311.11303-1-scott@jumpnowtek.com> (raw)

Applies to both zeus and dunfell

ERROR: Nothing RPROVIDES 'cryptodev-module-native' (but virtual:native:/home/scott/poky-zeus/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb RDEPENDS on or otherwise requires it)
ERROR: Required build target 'openssl' has no buildable providers.
Missing or unbuildable dependency chain was: ['openssl', 'rpm-native', 'python3-native', 'openssl-native', 'cryptodev-module-native']

Signed-off-by: Scott Ellis <scott@jumpnowtek.com>
---
 meta/recipes-connectivity/openssl/openssl_1.1.1f.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
index aa4ef6f48a..a952fae728 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
@@ -32,7 +32,7 @@ PACKAGECONFIG ?= ""
 PACKAGECONFIG_class-native = ""
 PACKAGECONFIG_class-nativesdk = ""
 
-PACKAGECONFIG[cryptodev-linux] = "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux,,cryptodev-module"
+PACKAGECONFIG[cryptodev-linux] = "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux"
 
 B = "${WORKDIR}/build"
 do_configure[cleandirs] = "${B}"
-- 
2.17.1


             reply	other threads:[~2020-04-30 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 20:23 Scott Ellis [this message]
2020-04-30 21:37 ` [yocto][PATCH] openssl: Fix dependency loop with PACKAGECONFIG cryptodev-linux Denys Dmytriyenko
2020-05-01 13:48   ` Scott Ellis

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=20200430202311.11303-1-scott@jumpnowtek.com \
    --to=jumpnowtek@gmail.com \
    --cc=scott@jumpnowtek.com \
    --cc=yocto@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 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.