From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH] linux-custom: Make tracing more consistent
Date: Mon, 11 Jul 2022 19:19:21 +0200 [thread overview]
Message-ID: <d55a4ee5-9560-07e3-151d-b175ba637c5e@siemens.com> (raw)
In-Reply-To: <15ba3bbe-85ea-1957-0a4f-f3599b932488@siemens.com>
On 11.07.22 19:02, Jan Kiszka wrote:
> On 11.07.22 15:07, Henning Schild wrote:
>> Am Sun, 10 Jul 2022 22:51:31 +0200
>> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
>>
>>> 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
>>
>> Maybe make that
>> printenv | grep -q BB_VERBOSE_LOGS && set -x
>>
>> as seen in the common.sh for other debian packages
>
> Will try that.
>
Nope, BB_VERBOSE_LOGS does not make it into the sbuild environment.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-07-11 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 20:51 Jan Kiszka
2022-07-11 13:07 ` Henning Schild
2022-07-11 17:02 ` Jan Kiszka
2022-07-11 17:19 ` Jan Kiszka [this message]
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=d55a4ee5-9560-07e3-151d-b175ba637c5e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=henning.schild@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