From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 1/2] make kernel module build reproducible
Date: Thu, 19 Sep 2024 16:18:03 +0300 [thread overview]
Message-ID: <6c6b1495be89358d1af803461f6e49091883f7ec.camel@ilbers.de> (raw)
In-Reply-To: <20240913151642.374093-1-felix.moessbauer@siemens.com>
On Fri, 2024-09-13 at 17:16 +0200, 'Felix Moessbauer' via isar-users
wrote:
> The debug information of kernel modules contain absolute file paths
> into the builder schroot. To fix this, we inject a debug-prefix-map,
> similar to how it is already done for the kernel build. While doing
> that, we also enable the user to inject other KCFLAGS and KAFLAGS as
> well.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/recipes-kernel/linux-module/files/debian/rules.tmpl | 2 +-
> meta/recipes-kernel/linux-module/module.inc | 6 ++++++
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux-module/files/debian/rules.tmpl
> b/meta/recipes-kernel/linux-module/files/debian/rules.tmpl
> index bc4e09cb..7511a17d 100755
> --- a/meta/recipes-kernel/linux-module/files/debian/rules.tmpl
> +++ b/meta/recipes-kernel/linux-module/files/debian/rules.tmpl
> @@ -49,7 +49,7 @@ override_dh_auto_clean:
> $(MAKE) -C $(KDIR) M=${MODULE_DIR} clean
>
> override_dh_auto_build:
> - $(MAKE) -C $(KDIR) M=${MODULE_DIR} $(PARALLEL_MAKE) modules
> + $(MAKE) -C $(KDIR) M=${MODULE_DIR} $(PARALLEL_MAKE)
> KCFLAGS="${KCFLAGS}" KAFLAGS="${KAFLAGS}" modules
> ifneq ($(filter pkg.sign,$(DEB_BUILD_PROFILES)),)
> find . -name "*.ko" -print -exec $(KDIR)/scripts/sign-file
> ${SIGNATURE_HASHFN} ${SIGNATURE_KEYFILE} ${SIGNATURE_CERTFILE} {} \;
> endif
> diff --git a/meta/recipes-kernel/linux-module/module.inc
> b/meta/recipes-kernel/linux-module/module.inc
> index 229e6a5c..344dc50f 100644
> --- a/meta/recipes-kernel/linux-module/module.inc
> +++ b/meta/recipes-kernel/linux-module/module.inc
> @@ -48,6 +48,8 @@ TEMPLATE_VARS += " \
> KERNEL_TYPE \
> KERNEL_IMAGE_PKG \
> KERNEL_HEADERS_PKG \
> + KCFLAGS \
> + KAFLAGS \
> MODULE_DIR \
> DEBIAN_BUILD_DEPENDS \
> SIGNATURE_KEYFILE \
> @@ -55,6 +57,10 @@ TEMPLATE_VARS += " \
> SIGNATURE_HASHFN \
> PN"
>
> +# Add custom cflags to the kernel build
> +KCFLAGS ?= "-fdebug-prefix-map=${CURDIR}=. -fmacro-prefix-
> map=${CURDIR}=."
> +KAFLAGS ?= "-fdebug-prefix-map=${CURDIR}=."
> +
> do_prepare_build() {
> rm -rf ${S}/debian
> cp -r ${WORKDIR}/debian ${S}/
> --
> 2.39.2
>
Applied to next, thanks.
--
Best regards,
Uladzimir.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/6c6b1495be89358d1af803461f6e49091883f7ec.camel%40ilbers.de.
prev parent reply other threads:[~2024-09-19 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 15:16 'Felix Moessbauer' via isar-users
2024-09-13 15:16 ` [PATCH 2/2] strip debug information from kernel modules 'Felix Moessbauer' via isar-users
2024-09-19 13:18 ` Uladzimir Bely [this message]
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=6c6b1495be89358d1af803461f6e49091883f7ec.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=felix.moessbauer@siemens.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