From: Srinuvasan A <Srinuvasan_A@mentor.com>
To: <isar-users@googlegroups.com>, <amikan@ilbers.de>
Cc: <jan.kiszka@siemens.com>, Srinuvasan A <srinuvasan_a@mentor.com>
Subject: [PATCH] linux-custom: Update to BASE_DISTRO_CODENAME instead of DISTRO
Date: Thu, 22 Sep 2022 11:49:28 +0530 [thread overview]
Message-ID: <20220922061928.1977-1-Srinuvasan_A@mentor.com> (raw)
From: Srinuvasan A <srinuvasan_a@mentor.com>
Commit 4ffdf792 says, Switch custom kernel modules to use libssl3 by
default and left libssl1.1 dependency only for distros not yet
migrated, here they used overrides based on "DISTRO".
Here DISTRO is debian-bullseye or debian-buster and so on, downstream layers might define
their own DISTRO name.
Use the overrides based on "BASE_DISTRO_CODENAME" to pick up the exact version of libssl
for the corresponding DISTRO to better support downstream layers with custom DISTRO names.
Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
---
meta/recipes-kernel/linux/linux-custom.inc | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index 8581dc8..31840f1 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -1,8 +1,8 @@
# Custom kernel build
#
# This software is a part of ISAR.
-# Copyright (c) Siemens AG, 2018
-# Copyright (c) Mentor Graphics, a Siemens business, 2019
+# Copyright (c) Siemens AG, 2022
+# Copyright (c) Mentor Graphics, a Siemens business, 2022
#
# SPDX-License-Identifier: MIT
@@ -13,6 +13,8 @@ CHANGELOG_V = "${PV}+${PR}"
DESCRIPTION ?= "Custom kernel"
MAINTAINER ?= "isar-users <isar-users@googlegroups.com>"
+OVERRIDES_append = ":${BASE_DISTRO_CODENAME}"
+
KBUILD_DEPENDS ?= "build-essential:native, \
libelf-dev:native, \
libncurses-dev:native, \
@@ -30,9 +32,9 @@ KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools | linux-initramfs-tool, \
linux-base (>= 4.3~),"
LIBSSL_DEP = "libssl3"
-LIBSSL_DEP_debian-stretch = "libssl1.1"
-LIBSSL_DEP_debian-buster = "libssl1.1"
-LIBSSL_DEP_debian-bullseye = "libssl1.1"
+LIBSSL_DEP_stretch = "libssl1.1"
+LIBSSL_DEP_buster = "libssl1.1"
+LIBSSL_DEP_bullseye = "libssl1.1"
KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, \
${LIBSSL_DEP},"
--
2.25.1
next reply other threads:[~2022-09-22 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHYzzdafU+zAaufNESZAMqViN9X/63vz2pQ>
2022-09-22 6:19 ` Srinuvasan A [this message]
2022-09-23 9:33 ` Anton Mikanovich
2022-09-23 10:28 ` [PATCH] bitbake.conf: Add BASE_DISTRO_CODENAME in OVERRIDES variable Srinuvasan A
2022-09-25 8:27 ` Moessbauer, Felix
2022-09-26 9:55 ` Srinuvasan Arjunan
2022-09-26 10:03 ` Anton Mikanovich
2022-09-28 9:22 ` Anton Mikanovich
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=20220922061928.1977-1-Srinuvasan_A@mentor.com \
--to=srinuvasan_a@mentor.com \
--cc=amikan@ilbers.de \
--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