From: Jan Kiszka <jan.kiszka@siemens.com>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] linux-custom: fix for kernels without modules
Date: Tue, 26 Feb 2019 17:53:27 +0100 [thread overview]
Message-ID: <64c964bc-91a7-30c7-2ce7-238bb86396c9@siemens.com> (raw)
In-Reply-To: <1551199590-199-1-git-send-email-Cedric_Hombourger@mentor.com>
On 26.02.19 17:46, Cedric Hombourger wrote:
> build-kernel.sh would try to create a .fresh_install file in the
> /lib/modules/${PV} folder to replicate Debian's postinst magic
> but would fail when the custom kernel is configured without any
> modules. Create /lib/modules/${PV} before .fresh_install to make
> sure its target directory exists.
>
> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> ---
> meta/recipes-kernel/linux/files/build-kernel.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-kernel/linux/files/build-kernel.sh b/meta/recipes-kernel/linux/files/build-kernel.sh
> index 6e4d347..842b585 100644
> --- a/meta/recipes-kernel/linux/files/build-kernel.sh
> +++ b/meta/recipes-kernel/linux/files/build-kernel.sh
> @@ -76,6 +76,7 @@ dpkg-gencontrol -crepack/debian/control \
> -DArchitecture=$target_arch
>
> # Add Debian-like link installation to postinst
> +mkdir -p ${REPACK_LINUX_IMAGE_DIR}/lib/modules/${PV}
> touch "${REPACK_LINUX_IMAGE_DIR}/lib/modules/${PV}/.fresh-install"
> sed -i "${REPACK_LINUX_IMAGE_DIR}/DEBIAN/postinst" \
> -e "/^set -e$/a\\
>
Makes sense, looks good.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-26 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:46 Cedric Hombourger
2019-02-26 16:53 ` Jan Kiszka [this message]
2019-03-14 19:19 ` 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=64c964bc-91a7-30c7-2ce7-238bb86396c9@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=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