From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: A possible bug into linux-custom.inc
Date: Mon, 19 Sep 2022 09:20:49 +0200 [thread overview]
Message-ID: <20220919092049.197767b3@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO7Z0XCza+=pYiT_oU6Sbo-8O6rUy8piAf2v3JE87D-qLw@mail.gmail.com>
Am Sun, 18 Sep 2022 22:04:00 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> 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
Well touching isar is not ideal, you rather want to find a solution
that overrides the bits from isar. Maybe apply a patch to that
debian-folder instead of bringing a modified copy.
I recently tried the same with a custom rules file for a module and
found that the main debian/rules would always win. So i decided to
bring my version in under another name and overwrite it in an
additional task.
SRC_URI += "file://debian/my_rules.tmpl"
do_my_rules() {
mv ${WORKDIR}/debian/my_rules.tmpl ${WORKDIR}/debian/rules.tmpl
}
addtask my_rules after do_unpack before do_transform_template
You could also tell us what you need to change in those original files
and why, maybe your case calls for a patch.
The inc should allow for most common changes people might want, if your
case is not yet supported that is interesting.
regards,
Henning
> 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.
>
next prev parent reply other threads:[~2022-09-19 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 20:04 Roberto A. Foglietta
2022-09-18 22:06 ` Roberto A. Foglietta
2022-09-19 7:20 ` Henning Schild [this message]
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=20220919092049.197767b3@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@gmail.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