From: Uladzimir Bely <ubely@ilbers.de>
To: venkata.pyla@toshiba-tsip.com, isar-users@googlegroups.com
Subject: Re: [PATCH] linux: remove debug paths in assembly compilations for repro builds
Date: Fri, 19 May 2023 07:14:48 +0300 [thread overview]
Message-ID: <5bd819d7fbec74dbd1ea312812731e5b6e5b9d55.camel@ilbers.de> (raw)
In-Reply-To: <20230509062040.13244-1-venkata.pyla@toshiba-tsip.com>
On Tue, 2023-05-09 at 11:50 +0530, venkata.pyla@toshiba-tsip.com wrote:
> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>
> vmlinux file is not reproducible in case of arm architectures, where
> the
> assembly files are compiled with debug info included with build
> paths,
> so use `-fdebug-prefix-map` to substitute the paths and produce bit
> identical builds.
>
> Signed-off-by: venkata pyla <venkata.pyla@toshiba-tsip.com>
> ---
> meta/recipes-kernel/linux/files/debian/isar/build.tmpl | 2 +-
> meta/recipes-kernel/linux/linux-custom.inc | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
Applied to next, thanks.
prev parent reply other threads:[~2023-05-19 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 6:20 venkata.pyla
2023-05-09 6:34 ` MOESSBAUER, Felix
2023-05-19 4:14 ` 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=5bd819d7fbec74dbd1ea312812731e5b6e5b9d55.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=venkata.pyla@toshiba-tsip.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