From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Subject: A possible bug into linux-custom.inc
Date: Sun, 18 Sep 2022 22:04:00 +0200 [thread overview]
Message-ID: <CAJGKYO7Z0XCza+=pYiT_oU6Sbo-8O6rUy8piAf2v3JE87D-qLw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Hi all,
Considering the last commit by now
dd8157136f63a665b3002ab99d2fe16db117d9fc
then this files includes a debian directory
grep file:// isar/meta/recipes-kernel/linux/linux-custom.inc
SRC_URI += "file://debian"
I created my own layer with a kernel recipe with my files/debian folder
because I want some changes and then I tried - cleaning everything sensible
- but just the isar debian dir is copied in place. Thus, I moved the isar
debian folder
mv isar/meta/recipes-kernel/linux/files/debian
isar/meta/recipes-kernel/linux/files/debian.bak
Then I cleaned and tried to build. This time, the correct debian folder has
been copied in place.
I think this is a bug and I wish to receive some help to fix it. Here
following the recipe
require recipes-kernel/linux/linux-custom.inc
KBUILD_DEPENDS += " dwarves"
KERNEL_DEFCONFIG = "debian-amd64-rt-defconfig"
SRC_URI += "
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/snapshot/linux-cip-${PV}.tar.gz
"
SRC_URI[sha256sum] =
"9a45929d91ebaddbf6a0ef29750775e33d3c3f56f42f0a9e95e77e5b4eba3c6e"
SRC_URI += "file://${KERNEL_DEFCONFIG}"
S = "${WORKDIR}/linux-cip-${PV}"
Thanks, R.
[-- Attachment #2: Type: text/html, Size: 1649 bytes --]
next reply other threads:[~2022-09-18 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 20:04 Roberto A. Foglietta [this message]
2022-09-18 22:06 ` Roberto A. Foglietta
2022-09-19 7:20 ` Henning Schild
2022-09-19 9:14 ` Roberto A. Foglietta
2022-09-19 11:33 ` Roberto A. Foglietta
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='CAJGKYO7Z0XCza+=pYiT_oU6Sbo-8O6rUy8piAf2v3JE87D-qLw@mail.gmail.com' \
--to=roberto.foglietta@gmail.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