From: Henning Schild <henning.schild@siemens.com>
To: Srinuvasan Arjunan <srinuvasan_a@mentor.com>
Cc: <isar-users@googlegroups.com>, <cedric.hombourger@siemens.com>,
Srinuvasan A <srinuvasan.a@siemens.com>
Subject: Re: [PATCH] linux: add "dwarves" to KBUILD_DEPENDS
Date: Wed, 28 Jun 2023 12:53:20 +0200 [thread overview]
Message-ID: <20230628125320.192f384e@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230628033910.2283445-1-srinuvasan_a@mentor.com>
Am Wed, 28 Jun 2023 09:09:10 +0530
schrieb Srinuvasan Arjunan <srinuvasan_a@mentor.com>:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
>
> When we build custom 5.10.175-cip29 kernel
> in one of the downstream layer we faced below error:
>
> `BTF: .tmp_vmlinux.btf: pahole (pahole) is not available
> Failed to generate BTF for vmlinux
> Try to disable CONFIG_DEBUG_INFO_BTF`
>
> hence install "dwarves" package as a dependency in sbuild-chroot
> when we build custom kernels.
This commit message is rather specific and could be more generic, but i
think the patch itself is fine.
Stock debian kernels have CONFIG_DEBUG_INFO_BTF enabled so it is kind of
likely that pahole will be needed at build time.
Henning
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
> meta/recipes-kernel/linux/linux-custom.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc
> b/meta/recipes-kernel/linux/linux-custom.inc index 1404ab0..f255d68
> 100644 --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -21,6 +21,7 @@ KBUILD_DEPENDS ?= "build-essential:native, \
> bc, \
> bison, \
> cpio, \
> + dwarves, \
> flex, \
> git, \
> kmod, \
next prev parent reply other threads:[~2023-06-28 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 3:39 Srinuvasan Arjunan
2023-06-28 10:53 ` Henning Schild [this message]
2023-07-04 10:00 ` Srinuvasan Arjunan
2023-07-11 6:39 ` Uladzimir Bely
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=20230628125320.192f384e@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=cedric.hombourger@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=srinuvasan.a@siemens.com \
--cc=srinuvasan_a@mentor.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