public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: [PATCH] linux-custom: Make tracing more consistent
Date: Sun, 10 Jul 2022 22:51:31 +0200	[thread overview]
Message-ID: <7336ac63-14ba-cd26-08ba-9c121bc29df3@siemens.com> (raw)

From: Jan Kiszka <jan.kiszka@siemens.com>

Include more of the do_build and anything of do_configure into the trace
log.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 meta/recipes-kernel/linux/files/debian/isar/build.tmpl     | 6 +++---
 meta/recipes-kernel/linux/files/debian/isar/configure.tmpl | 3 +++
 2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/files/debian/isar/build.tmpl b/meta/recipes-kernel/linux/files/debian/isar/build.tmpl
index 550bdc67..65261e41 100644
--- a/meta/recipes-kernel/linux/files/debian/isar/build.tmpl
+++ b/meta/recipes-kernel/linux/files/debian/isar/build.tmpl
@@ -10,6 +10,9 @@ do_build() {
     # Print a few things that are of particular interest
     print_settings
 
+    # Trace what we do here
+    set -x
+
     # Process existing kernel configuration to make sure it is complete
     # (use defaults for options that were not specified)
     ${MAKE} O=${KERNEL_BUILD_DIR} olddefconfig prepare
@@ -18,9 +21,6 @@ do_build() {
     KR=$(${MAKE} O=${KERNEL_BUILD_DIR} -s --no-print-directory kernelrelease)
     sed -i "s/@KR@/${KR}/g" ${S}/debian/control ${S}/debian/linux-image-${KERNEL_NAME_PROVIDED}.*
 
-    # Trace what we do here
-    set -x
-
     # Build the Linux kernel
     ${MAKE} O=${KERNEL_BUILD_DIR} ${PARALLEL_MAKE}
 
diff --git a/meta/recipes-kernel/linux/files/debian/isar/configure.tmpl b/meta/recipes-kernel/linux/files/debian/isar/configure.tmpl
index 58f10326..389c9a85 100644
--- a/meta/recipes-kernel/linux/files/debian/isar/configure.tmpl
+++ b/meta/recipes-kernel/linux/files/debian/isar/configure.tmpl
@@ -7,6 +7,9 @@
 
 do_configure() {
 
+    # Trace what we do here
+    set -x
+
     # Process kernel config target and fragments
     ${MAKE} O=${KERNEL_BUILD_DIR} ${KERNEL_CONFIG_TARGET}
     ./scripts/kconfig/merge_config.sh -O ${KERNEL_BUILD_DIR}/ \
-- 
2.35.3

             reply	other threads:[~2022-07-10 20:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 20:51 Jan Kiszka [this message]
2022-07-11 13:07 ` Henning Schild
2022-07-11 17:02   ` Jan Kiszka
2022-07-11 17:19     ` Jan Kiszka
2022-07-12  7:43       ` Henning Schild
2022-07-19 18:55 ` Anton Mikanovich

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=7336ac63-14ba-cd26-08ba-9c121bc29df3@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