From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 06/15] reproducibility/linux: inhibit build-id
Date: Sat, 19 Nov 2016 15:04:03 +0100 [thread overview]
Message-ID: <1479588390.8yanCXY4Bm@sagittea> (raw)
In-Reply-To: <0274904d-a7d0-4ac1-dd28-73f920a77fa0@mind.be>
On Saturday 19 November 2016 10:31:51 Arnout Vandecappelle wrote:
>
> On 18-11-16 10:10, J?r?me Pouiller wrote:
> > By default, Linux kernel enable 'build-id'. 'build-id' tends to add random
> > bytes in section .notes of kernel image[1]:
>
> Err, no, these are not random bytes, these are a sha1 of the content of the
> file. If the build ID changes, it means the content has changed.
>
> One common way that the build ID can differ while the output files don't differ
> is because of the source path that is recorded in the debug sections (which are
> stripped in the end). But I think that reproducible builds when the source path
> differs are very far away at this point...
Oh, you are right! I didn't understood why my build-id changes while all
sections was identical. In fact, in some circumstances, symbol order in
debug sections is not defined. I don't know yet exactly why nor how to
fix it.
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2016-11-19 14:04 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 9:10 [Buildroot] [PATCH v2 00/15] Reproducible builds Jérôme Pouiller
2016-11-18 9:10 ` [Buildroot] [PATCH v2 01/15] reproducibility: generate SOURCE_DATE_EPOCH Jérôme Pouiller
2016-11-18 11:33 ` Thomas Petazzoni
2016-11-18 13:48 ` Jérôme Pouiller
2016-11-19 8:51 ` Arnout Vandecappelle
2016-11-19 9:51 ` Thomas Petazzoni
2016-11-19 10:01 ` Arnout Vandecappelle
2016-11-19 8:40 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 02/15] reproducible: fix DATE/TIME macros in toolchain-wrapper Jérôme Pouiller
2016-11-18 11:37 ` Thomas Petazzoni
2016-11-18 13:46 ` Jérôme Pouiller
2016-11-18 9:10 ` [Buildroot] [PATCH v2 03/15] reproducible: add '-n' to gzip invocations Jérôme Pouiller
2016-11-18 11:38 ` Thomas Petazzoni
2016-11-19 9:02 ` Arnout Vandecappelle
2016-11-19 13:49 ` Jérôme Pouiller
2016-11-18 9:10 ` [Buildroot] [PATCH v2 04/15] fs/tar: make results reproducible Jérôme Pouiller
2016-11-18 11:40 ` Thomas Petazzoni
2016-11-18 13:02 ` Jérôme Pouiller
2016-11-18 13:29 ` Thomas Petazzoni
2016-11-18 13:44 ` Jérôme Pouiller
2016-11-18 21:28 ` Thomas Petazzoni
2016-11-19 8:33 ` Arnout Vandecappelle
2016-11-19 13:56 ` Jérôme Pouiller
2016-11-19 9:12 ` Arnout Vandecappelle
2016-11-19 13:59 ` Jérôme Pouiller
2016-11-18 9:10 ` [Buildroot] [PATCH v2 05/15] reproducibility/linux: override build timestamp Jérôme Pouiller
2016-11-18 11:40 ` Thomas Petazzoni
2016-11-19 13:53 ` Jérôme Pouiller
2016-11-19 16:10 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 06/15] reproducibility/linux: inhibit build-id Jérôme Pouiller
2016-11-19 9:31 ` Arnout Vandecappelle
2016-11-19 14:04 ` Jérôme Pouiller [this message]
2016-11-18 9:10 ` [Buildroot] [PATCH v2 07/15] reproducibility/busybox: disable build timestamps Jérôme Pouiller
2016-11-18 11:41 ` Thomas Petazzoni
2016-11-19 9:32 ` Arnout Vandecappelle
2016-11-19 9:33 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 08/15] reproducible: lock modification times in $TARGET_DIR Jérôme Pouiller
2016-11-18 11:43 ` Thomas Petazzoni
2016-11-19 9:39 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 09/15] fakedate: new package Jérôme Pouiller
2016-11-18 11:48 ` Thomas Petazzoni
2016-11-19 13:24 ` Jérôme Pouiller
2016-11-19 10:21 ` Arnout Vandecappelle
2016-11-19 13:06 ` Jérôme Pouiller
2016-11-19 13:26 ` Arnout Vandecappelle
2016-11-19 13:38 ` Jérôme Pouiller
2016-11-22 10:59 ` Jérôme Pouiller
2016-11-18 9:10 ` [Buildroot] [PATCH v2 10/15] reproducible: enable fakedate Jérôme Pouiller
2016-11-18 11:49 ` Thomas Petazzoni
2016-11-18 13:53 ` Jérôme Pouiller
2016-11-19 10:22 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 11/15] python2: generate reproducible .pyc Jérôme Pouiller
2016-11-19 10:41 ` Arnout Vandecappelle
2016-11-19 12:35 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 12/15] python3: " Jérôme Pouiller
2016-11-18 9:10 ` [Buildroot] [PATCH v2 13/15] python2: remove full path from .pyc Jérôme Pouiller
2016-11-19 12:38 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 14/15] python3: " Jérôme Pouiller
2016-11-19 12:39 ` Arnout Vandecappelle
2016-11-18 9:10 ` [Buildroot] [PATCH v2 15/15] reproducible: improve help text Jérôme Pouiller
2016-11-19 12:45 ` 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=1479588390.8yanCXY4Bm@sagittea \
--to=jezz@sysmic.org \
--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