From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Reproducible-builds] [PATCH] build: create time and date independent binary
Date: Sun, 19 Jul 2015 17:00:08 +0200 [thread overview]
Message-ID: <1437318008.3542.14.camel@collins> (raw)
In-Reply-To: <87pp3oe1bl.fsf@aikidev.net>
Le dimanche 19 juillet 2015 ? 06:14 -0700, Vagrant Cascadian a ?crit :
> 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...
We came up with something similar last week. This is not actually
sufficient, but close. I will submit what I have to the U-Boot mailing
list soon (hopefully, later today), feel free to review it there and
import it to Debian.
> 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.
Native builds don't seem realistic given the many different
architectures that U-Boot supports, unless done with virtualisation (see
my other email from today).
Now that I think about it, maybe virtualisation would require simply too
many VMs to setup.
Either way, we can always try to add a toolchain build script to U-Boot.
--
Paul Kocialkowski, Replicant developer
Replicant is a fully free Android distribution running on several
devices, a free software mobile operating system putting the emphasis on
freedom and privacy/security.
Website: http://www.replicant.us/
Blog: http://blog.replicant.us/
Wiki/tracker/forums: http://redmine.replicant.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150719/a9acaffd/attachment.sig>
next prev parent reply other threads:[~2015-07-19 15:00 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 [this message]
2015-07-19 15:18 ` Holger Levsen
2015-07-20 6:23 ` Heiko Schocher
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=1437318008.3542.14.camel@collins \
--to=contact@paulk.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.