Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Atharva Lele <itsatharva@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] autobuild-run: use different output directories for reproducible builds testing
Date: Wed, 07 Aug 2019 11:32:52 +0530	[thread overview]
Message-ID: <8265074.T7ehH8mb2W@msi-manjaro> (raw)
In-Reply-To: <20190806213724.33e3f302@windsurf.home>

On Wednesday, August 7, 2019 1:07:24 AM IST Thomas Petazzoni wrote:
> Hello,
> 
> On Tue,  6 Aug 2019 23:42:46 +0530
> 
> Atharva Lele <itsatharva@gmail.com> wrote:
> > Having different output directories increases variation in the build.
> > 
> > This commit also changes the directory name of the single output directory
> > to "output-1", as having varied length names for output directories
> > introduces a lot of reproducibility issues.
> > 
> > Official Debian efforts also currently use same length names for different
> > directories: "/build/1st/$pkg-$ver" and "/build/$pkg-$ver/2nd"
> > Cfr: https://tests.reproducible-builds.org/debian/index_variations.html
> 
> Is this an intermediate step, with the long term goal of supporting
> output directories of different length, or is this a limitation that we
> will have "forever" ?

Reproducible-Builds has proposed a spec called BUILD_PATH_PREFIX_MAP to help 
with this. However, that is still in the works and not fully solved yet. (As 
told to Yann and I on the #reproducible-builds IRC)

See: https://wiki.debian.org/ReproducibleBuilds/GCC-build-path and https://
reproducible-builds.org/specs/build-path-prefix-map/

So I think until further work is done on BUILD_PATH_PREFIX_MAP, we will have 
to stay with output directories of same length.

> Thanks!
> 
> Thomas

Regards,
Atharva Lele

  reply	other threads:[~2019-08-07  6:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 18:12 [Buildroot] [PATCH 1/6] autobuild-run: use different output directories for reproducible builds testing Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 2/6] autobuild-run: make prepare_build() clean the output directory used for reproducibility testing Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 3/6] autobuild-run: fix cross tools prefix for diffoscope Atharva Lele
2019-08-06 20:18   ` Thomas Petazzoni
2019-08-06 18:12 ` [Buildroot] [PATCH 4/6] autobuild-run: make diffoscope output to a JSON-formatted file Atharva Lele
2019-08-06 19:40   ` Thomas Petazzoni
2019-08-07  6:12     ` Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 5/6] autobuild-run: initial implementation of get_reproducibility_failure_reason() Atharva Lele
2019-08-06 20:21   ` Thomas Petazzoni
2019-08-07  6:07     ` Atharva Lele
2019-08-06 18:12 ` [Buildroot] [PATCH 6/6] autobuild-run: account for reproducibility failures in get_failure_reason() Atharva Lele
2019-08-06 19:37 ` [Buildroot] [PATCH 1/6] autobuild-run: use different output directories for reproducible builds testing Thomas Petazzoni
2019-08-07  6:02   ` Atharva Lele [this message]
2019-08-07  8:33     ` Thomas Petazzoni

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=8265074.T7ehH8mb2W@msi-manjaro \
    --to=itsatharva@gmail.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