From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
To: <isar-users@googlegroups.com>, <jan.kiszka@siemens.com>
Cc: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
Subject: [PATCH v5 3/4] meta: u-boot: Prepare for newer versions
Date: Tue, 1 Feb 2022 17:27:12 +0530 [thread overview]
Message-ID: <20220201115713.3062835-4-Vijaikumar_Kanagarajan@mentor.com> (raw)
In-Reply-To: <20220201115713.3062835-1-Vijaikumar_Kanagarajan@mentor.com>
Newer versions of u-boot require libssl-dev:native for compilation.
It also needs libssl-dev of the host architecture for cross compilation
of tools.
Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
---
meta/recipes-bsp/u-boot/u-boot-custom.inc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-bsp/u-boot/u-boot-custom.inc b/meta/recipes-bsp/u-boot/u-boot-custom.inc
index 5198809..dd69c00 100644
--- a/meta/recipes-bsp/u-boot/u-boot-custom.inc
+++ b/meta/recipes-bsp/u-boot/u-boot-custom.inc
@@ -41,7 +41,8 @@ python() {
d.setVar('U_BOOT_BUILD_PROFILES_remove', "config")
}
-DEBIAN_BUILD_DEPENDS ?= "bc, bison, flex, device-tree-compiler, git"
+DEBIAN_BUILD_DEPENDS ?= "bc, bison, flex, device-tree-compiler, git, \
+ libssl-dev:native, libssl-dev <tools>"
TEMPLATE_FILES = "debian/control.tmpl"
TEMPLATE_VARS += "MACHINE DEBIAN_BUILD_DEPENDS"
--
2.25.1
next prev parent reply other threads:[~2022-02-01 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 11:57 [PATCH v5 0/4] U-boot Refactor and update to 2022.01 Vijai Kumar K
2022-02-01 11:57 ` [PATCH v5 1/4] u-boot: Switch to use DEB_BUILD_PROFILES Vijai Kumar K
2022-02-01 12:54 ` Moessbauer, Felix
2022-02-01 19:03 ` vijai kumar
2022-02-01 11:57 ` [PATCH v5 2/4] meta-isar: u-boot: Migrate to U_BOOT_BUILD_PROFILES Vijai Kumar K
2022-02-01 11:57 ` Vijai Kumar K [this message]
2022-02-01 11:57 ` [PATCH v5 4/4] meta-isar: u-boot: Update to 2022.01 Vijai Kumar K
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=20220201115713.3062835-4-Vijaikumar_Kanagarajan@mentor.com \
--to=vijaikumar_kanagarajan@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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