From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-custom: Pin buster compat level to 10 to fix kernel builds
Date: Sun, 16 Feb 2025 11:01:08 +0300 [thread overview]
Message-ID: <57fb3307832e6995ff426ba5670b844eb716b69f.camel@ilbers.de> (raw)
In-Reply-To: <6c52b13f-0f6a-4749-8b4b-343b801bc431@siemens.com>
On Mon, 2025-02-03 at 11:54 +0100, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Compat level 12 of buster selects dh_dwz which breaks in that old
> version with certain kernels, e.g. like this:
>
> dwz: dwz.c:9255: recompute_abbrevs: Assertion `off == cu_size'
> failed.
> dh_dwz: dwz -q -- debian/linux-image-cip-
> dbg/usr/lib/debug/lib/modules/5.10.233-cip56/vmlinux died with signal
> 6
>
> As buster is LTS now, we take the low-risk path and switch back to
> the
> compat level the recipe was once validated again, rather than trying
> to
> resolve this and possibly more issues.
>
> Fixes: ca786c36bca9 ("meta/recipes-kernel: use debhelper-compat to
> generate compat file")
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta/recipes-kernel/linux/linux-custom.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-kernel/linux/linux-custom.inc
> b/meta/recipes-kernel/linux/linux-custom.inc
> index 77700a5d..d2fca3aa 100644
> --- a/meta/recipes-kernel/linux/linux-custom.inc
> +++ b/meta/recipes-kernel/linux/linux-custom.inc
> @@ -14,6 +14,9 @@ DESCRIPTION ?= "Custom kernel"
> MAINTAINER ?= "isar-users <isar-users@googlegroups.com>"
> DISTRIBUTOR ?= "ISAR"
>
> +# pinned due to known or possible issues with compat 12
> +DEBIAN_COMPAT:buster = "10"
> +
> KBUILD_DEPENDS ?= "build-essential:native, \
> libelf-dev:native, \
> libncurses-dev:native, \
> --
> 2.43.0
>
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 visit https://groups.google.com/d/msgid/isar-users/57fb3307832e6995ff426ba5670b844eb716b69f.camel%40ilbers.de.
prev parent reply other threads:[~2025-02-16 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 10:54 'Jan Kiszka' via isar-users
2025-02-14 13:40 ` 'Jan Kiszka' via isar-users
2025-02-16 8:01 ` 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=57fb3307832e6995ff426ba5670b844eb716b69f.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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