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] linux: add "git" to KBUILD_DEPENDS
Date: Sun, 26 Aug 2018 11:10:52 +0200	[thread overview]
Message-ID: <1535274652-191-1-git-send-email-Cedric_Hombourger@mentor.com> (raw)

Several build scripts from the kernel use "git" and in particular
scripts/setlocalversion. The latter is used to produce a version
string when we "make -s kernelrelease". My kernel builds would
sporadically fail with the PV check as the "+" sign appended by
kbuild would or would not be present in the "kernelrelease" output
if "git" was installed or not in the buildchroot. Get consistent
results by getting "git" installed into the buildchroot when we
build custom kernels.

Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.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 8438143..d75346e 100644
--- a/meta/recipes-kernel/linux/linux-custom.inc
+++ b/meta/recipes-kernel/linux/linux-custom.inc
@@ -24,7 +24,7 @@ inherit dpkg-base
 
 SRC_URI += "file://build-kernel.sh"
 
-KBUILD_DEPENDS ?= "libssl-dev libelf-dev bc"
+KBUILD_DEPENDS ?= "libssl-dev libelf-dev bc git"
 KERNEL_DEBIAN_DEPENDS ?= "initramfs-tools | linux-initramfs-tool, kmod, linux-base (>= 4.3~)"
 KERNEL_HEADERS_DEBIAN_DEPENDS ?= "libc6, libssl1.1"
 
-- 
2.11.0


             reply	other threads:[~2018-08-26  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26  9:10 Cedric Hombourger [this message]
2018-08-27  7:21 ` Jan Kiszka
2018-08-28 12:12 ` 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=1535274652-191-1-git-send-email-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