public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH 1/2] linux-custom: correct name of linux-libc-dev package
Date: Wed, 13 Apr 2022 14:02:55 +0200	[thread overview]
Message-ID: <20220413120256.165-2-Cedric_Hombourger@mentor.com> (raw)
In-Reply-To: <20220413120256.165-1-Cedric_Hombourger@mentor.com>

When checking whether to install libc headers, the package to check for
is linux-libc-dev, not linux-libc-headers. The typo caused the generated
linux-libc-dev to be (almost) empty.

Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
---
 meta/recipes-kernel/linux/files/debian/isar/install.tmpl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl
index 69fb88d..4c8c889 100644
--- a/meta/recipes-kernel/linux/files/debian/isar/install.tmpl
+++ b/meta/recipes-kernel/linux/files/debian/isar/install.tmpl
@@ -200,7 +200,7 @@ kernel_headers() {
 
 install_headers() {
     headers_check
-    [ -z ${kern_pkgs["linux-libc-headers"]} ] || libc_headers
+    [ -z ${kern_pkgs["linux-libc-dev"]} ] || libc_headers
     kernel_headers
 }
 
-- 
2.30.2


  reply	other threads:[~2022-04-13 12:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 12:02 [PATCH 0/2] linux-custom: fix building of the " Cedric Hombourger
2022-04-13 12:02 ` Cedric Hombourger [this message]
2022-04-13 12:02 ` [PATCH 2/2] linux-custom: add rsync to build dependencies Cedric Hombourger
2022-05-05 10:17 ` [PATCH 0/2] linux-custom: fix building of the linux-libc-dev package 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=20220413120256.165-2-Cedric_Hombourger@mentor.com \
    --to=cedric_hombourger@mentor.com \
    --cc=isar-users@googlegroups.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