From: Jan Kiszka <jan.kiszka@web.de>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH] linux-custom: Add further build dependencies for recent kernels
Date: Sun, 30 Sep 2018 18:54:51 +0200 [thread overview]
Message-ID: <43a5a1b9-b032-36ff-0401-9d05c7198f3b@web.de> (raw)
From: Jan Kiszka <jan.kiszka@siemens.com>
Seen as needed with 4.19-rc5, might affect older kernels as well.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/recipes-kernel/linux/linux-custom.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/linux-custom.inc b/meta/recipes-kernel/linux/linux-custom.inc
index d7595e4..34c9a62 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -22,7 +22,7 @@ inherit dpkg-base
SRC_URI += "file://build-kernel.sh"
-KBUILD_DEPENDS ?= "libssl-dev libelf-dev bc git kmod"
+KBUILD_DEPENDS ?= "build-essential:native libssl-dev libelf-dev bc git kmod bison flex cpio"
KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools | linux-initramfs-tool, kmod, linux-base (>= 4.3~)"
KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, libssl1.1"
--
2.16.4
next reply other threads:[~2018-09-30 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 16:54 Jan Kiszka [this message]
2018-10-01 10:51 ` Maxim Yu. Osipov
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=43a5a1b9-b032-36ff-0401-9d05c7198f3b@web.de \
--to=jan.kiszka@web.de \
--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