From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] autobuild-run: initial implementation of do_reproducible_build()
Date: Fri, 7 Jun 2019 10:33:38 +0200 [thread overview]
Message-ID: <20190607103338.0431cf9e@windsurf> (raw)
In-Reply-To: <20190607064657.3571-2-itsatharva@gmail.com>
Hello,
On Fri, 7 Jun 2019 12:16:56 +0530
Atharva Lele <itsatharva@gmail.com> wrote:
> This new function will call do_build() twice to produce two builds
> and then check their reproducibility
>
> Signed-off-by: Atharva Lele <itsatharva@gmail.com>
So, if I read the implementation correctly, in this first step, we
build twice in the same output path, i.e the only variation between the
first and the second build is the time at which the build takes place.
We discussed on IRC that we could easily also change the output path
(i.e build location) between the first and second build. But perhaps
this is something that is planned to do in a second step, and you want
to make progress with a simpler initial solution ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-07 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 6:46 [Buildroot] [PATCH v2 1/3] autobuild-run: initial implementation of check_reproducibility() Atharva Lele
2019-06-07 6:46 ` [Buildroot] [PATCH v2 2/3] autobuild-run: initial implementation of do_reproducible_build() Atharva Lele
2019-06-07 8:33 ` Thomas Petazzoni [this message]
2019-06-07 8:39 ` Arnout Vandecappelle
2019-06-07 8:44 ` Thomas Petazzoni
2019-06-07 8:40 ` Atharva Lele
2019-06-08 11:40 ` Arnout Vandecappelle
2019-06-07 6:46 ` [Buildroot] [PATCH v2 3/3] autobuild-run: do reproducible builds tests if BR2_REPRODUCIBLE=y Atharva Lele
2019-06-08 11:46 ` Arnout Vandecappelle
2019-06-08 11:37 ` [Buildroot] [PATCH v2 1/3] autobuild-run: initial implementation of check_reproducibility() Arnout Vandecappelle
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=20190607103338.0431cf9e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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