meta-arago.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Aniket Limaye <a-limaye@ti.com>
To: <meta-arago@lists.yoctoproject.org>
Cc: <reatmon@ti.com>, Denys Dmytriyenko <denys@konsulko.com>,
	Aniket Limaye <a-limaye@ti.com>
Subject: [meta-arago][kirkstone][PATCH] strongswan: fix missing strongswap-plugin-mgf1
Date: Tue, 16 Jan 2024 20:19:01 +0530	[thread overview]
Message-ID: <20240116144901.1037514-1-a-limaye@ti.com> (raw)

From: Denys Dmytriyenko <denys@konsulko.com>

Fix tisdk-default-image do_rootfs errors after [1]

cherry-pick commit from master branch: 922420df0f445c8f7c830965f88a5fc566eb6ff0

Upstream strongswan recipe in meta-openembedded/meta-networking sets
runtime dependency for MGF1 plugin, but it is not enabled by default
and hence no such package gets produced.

[1]: https://git.openembedded.org/meta-openembedded/commit/meta-networking/recipes-support/strongswan?h=kirkstone&id=dd23a9930360f540c919ddfd35fd1f6088174ef3

Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
---
 .../recipes-support/strongswan/strongswan_%.bbappend             | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-arago-distro/recipes-support/strongswan/strongswan_%.bbappend b/meta-arago-distro/recipes-support/strongswan/strongswan_%.bbappend
index 0af8c9c2..ae313c74 100644
--- a/meta-arago-distro/recipes-support/strongswan/strongswan_%.bbappend
+++ b/meta-arago-distro/recipes-support/strongswan/strongswan_%.bbappend
@@ -8,6 +8,7 @@ PACKAGECONFIG = "charon curl openssl stroke sqlite3 \
 EXTRA_OECONF += " \
         --enable-ctr \
         --enable-pkcs11 \
+        --enable-mgf1 \
 "
 
 SRC_URI += "file://pkcs11_plugin.conf"
-- 
2.34.1



                 reply	other threads:[~2024-01-16 14:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240116144901.1037514-1-a-limaye@ti.com \
    --to=a-limaye@ti.com \
    --cc=denys@konsulko.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    /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).