From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Reproducible-builds] [PATCH] build: create time and date independent binary
Date: Mon, 20 Jul 2015 08:23:09 +0200 [thread overview]
Message-ID: <55AC93CD.8020109@denx.de> (raw)
In-Reply-To: <87pp3oe1bl.fsf@aikidev.net>
Hello Vagrant,
Am 19.07.2015 um 15:14 schrieb Vagrant Cascadian:
> On 2015-07-19, Holger Levsen wrote:
>>>> All this said, if you send me patches, I will probably deploy them as I'm
>>>> very curious and more reproducibility efforts are good :-) We can can
>>>> always decide to remove or move them later.
>>>
>>> I wish to make all contributions upstream. What would really help at
>>> first would be to have all targets built regularly to see where work is
>>> needed. This is where I think the Debian infrastructure could help, in a
>>> similar way as what was started for Coreboot.
>
> FWIW, I was planning on including this patch to u-boot in the next
> upload to Debian:
>
> https://anonscm.debian.org/cgit/collab-maint/u-boot.git/tree/debian/patches/use-date-from-debian-changelog.patch?h=experimental-2015.07
>
> I *think* that actually makes u-boot build reproducibly with Debian's
> reproducible builds toolchain when SOURCE_DATE_EPOCH is set, but I
> haven't tested it fully. I might have missed some other sources of
> non-determinism...
>
>
> Hoping to get some armhf buildd nodes up an running soonish... although
> it should also be buildable with the cross-toolchains, if the
> reproducible buildds coulld be made to support that.
Did you see my v2 patch [1] for u-boot?
It also builds now u-boot images created with mkimage reproducible ...
If I interpret your patch from above correct, you add with
SOURCE_DATE_EPOCH a specific fix timestamp?
I think, this could be included to my approach too ...
If SOURCE_DATE_EPOCH is defined, use it, fi not defined
define U_BOOT_DATE, U_BOOT_TIME and U_BOOT_TZ
with my default settings from [1] ...
All only if CONFIG_SYS_EXACT_BINARY is set in the u-boot
config of course ...
What do you think?
bye,
Heiko
[1] http://patchwork.ozlabs.org/patch/487530/
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2015-07-20 6:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 15:31 [U-Boot] [PATCH] build: create time and date independent binary Heiko Schocher
2015-06-12 20:21 ` Paul Kocialkowski
2015-06-13 9:10 ` [U-Boot] [Reproducible-builds] " Holger Levsen
2015-06-13 18:26 ` Paul Kocialkowski
2015-07-19 12:36 ` Holger Levsen
2015-07-19 13:14 ` Vagrant Cascadian
2015-07-19 15:00 ` Paul Kocialkowski
2015-07-19 15:18 ` Holger Levsen
2015-07-20 6:23 ` Heiko Schocher [this message]
2015-07-20 8:03 ` Paul Kocialkowski
2015-07-19 14:55 ` Paul Kocialkowski
2015-07-19 15:47 ` Holger Levsen
2015-07-19 16:39 ` Paul Kocialkowski
2015-06-15 13:04 ` [U-Boot] " Heiko Schocher
2015-06-13 19:40 ` Chris Kuethe
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=55AC93CD.8020109@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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