From: Jan Kiszka <jan.kiszka@siemens.com>
To: <isar-users@googlegroups.com>
Subject: Re: [PATCH] sbuild: Fix low hit ratio for ccache on linux kernel rebuild
Date: Sun, 17 Jul 2022 20:53:04 +0200 [thread overview]
Message-ID: <a12a07ea-a000-2c9c-2dac-d0aa32f6e17e@siemens.com> (raw)
In-Reply-To: <YtFv6EeZ+P5xgArw@ilbers.de>
On 15.07.22 15:47, Baurzhan Ismagulov wrote:
> Hello Felix,
>
> On Fri, Jul 15, 2022 at 01:27:27PM +0000, Moessbauer, Felix wrote:
>> Please also have a look at the reproducibility section of dpkg-buildflags.
>> The only reason the kernel is affected from this is, that the kbuild only uses KCFLAGS, not CFLAGS.
>> At least the flags about reproducibility should be added to all kernel builds done via ISAR.
>
> IIUC, the non-reproducibility comes from the absolute paths in the debug info
> -- we'll have a look, maybe those could be replaced with relative ones.
>
> I haven't deeply looked at reproducible packages, could you please elaborate on
> the KCFLAGS vs. CFLAGS distinction mattering here?
>
https://www.kernel.org/doc/html/latest/kbuild/reproducible-builds.html
may explain more. I just learned from Ben Hutchings that following this
in our kernel recipe may not only resolve the absolute path topic but
would also allow to drop slow dh_strip_nondeterminism from our builds.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2022-07-17 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 11:27 Uladzimir Bely
2022-07-15 13:27 ` Moessbauer, Felix
2022-07-15 13:44 ` Uladzimir Bely
2022-07-15 13:50 ` Baurzhan Ismagulov
2022-07-15 14:48 ` Moessbauer, Felix
2022-07-15 13:47 ` Baurzhan Ismagulov
2022-07-17 18:53 ` Jan Kiszka [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=a12a07ea-a000-2c9c-2dac-d0aa32f6e17e@siemens.com \
--to=jan.kiszka@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