public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, stefan-koch@siemens.com
Subject: Re: [PATCH v2 0/4] Fix kernel build and propagation of linux-libc-dev
Date: Wed, 5 Aug 2026 10:42:13 +0200	[thread overview]
Message-ID: <53ac0299-ea0a-4260-b6bf-276ba3ff8991@ilbers.de> (raw)
In-Reply-To: <20260803083450.2048909-1-felix.moessbauer@siemens.com>

Applied to next, thanks.

Zhihang

On 8/3/26 10:34, 'Felix Moessbauer' via isar-users wrote:
> This series fixes the kernel build and the propagation of linux-libc-dev,
> which is enabled by setting KERNEL_LIBC_DEV_DEPLOY = "1".
>
> To ensure this does not silently break in the future, we add a test.
> As testing the actual build of the kernel is too expensive, we only test
> the propagation of the dependency via a parser test.
>
> Changes since v1:
>
> - p2: rework comments to better explain why some targets disable cross compile
> - p4: rework testcase by moving logic from cibase.py to citest.py
> - No functional changes compared to v1
>
> Best regards,
> Felix Moessbauer
> Siemens AG
>
> Felix Moessbauer (4):
>    kernel: drop implicit build dependency to build-essential
>    fix(kernel): restore building of linux-libc-dev
>    testsuite: emit output filenames in generate_dependency_graph
>    testsuite: add test for KERNEL_LIBC_DEV_DEPLOY
>
>   meta/classes-recipe/libctarget.bbclass        | 13 +++++
>   meta/classes-recipe/linux-kernel.bbclass      | 47 ++++++++++++++++---
>   .../linux/files/debian/control.tmpl           |  4 +-
>   .../linux/files/debian/isar/common.tmpl       |  6 ++-
>   .../linux/files/debian/isar/install.tmpl      |  9 ++++
>   testsuite/cibase.py                           | 15 ++++--
>   testsuite/citest.py                           | 36 ++++++++++++++
>   7 files changed, 118 insertions(+), 12 deletions(-)
>   create mode 100644 meta/classes-recipe/libctarget.bbclass
>

-- 
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/53ac0299-ea0a-4260-b6bf-276ba3ff8991%40ilbers.de.

      parent reply	other threads:[~2026-08-05  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  8:34 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` [PATCH v2 1/4] kernel: drop implicit build dependency to build-essential 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` [PATCH v2 2/4] fix(kernel): restore building of linux-libc-dev 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` [PATCH v2 3/4] testsuite: emit output filenames in generate_dependency_graph 'Felix Moessbauer' via isar-users
2026-08-03  8:34 ` [PATCH v2 4/4] testsuite: add test for KERNEL_LIBC_DEV_DEPLOY 'Felix Moessbauer' via isar-users
2026-08-05  8:42 ` Zhihang Wei [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=53ac0299-ea0a-4260-b6bf-276ba3ff8991@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=stefan-koch@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