From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Deterministic builds
Date: Thu, 05 May 2016 21:46:00 -0000 [thread overview]
Message-ID: <466e1bc4-94b6-8eb7-0ea8-59680838e549@cornell.edu> (raw)
In-Reply-To: <AC9BB4BE-DE9D-4AC3-8FB3-7B0E58851F03@etr-usa.com>
On 5/5/2016 4:26 PM, Warren Young wrote:
> On May 5, 2016, at 11:59 AM, Ken Brown <kbrown@cornell.edu> wrote:
>>
>> Ismail's suggestion did indeed produce deterministic builds in my setup. I built a large project with about 150 executables, changed a few source files, removed the build directory, rebuilt, and found that only the (expected) few executables changed.
>
> â¦and does it do the same on a very different system? e.g. Try it on both 64-bit Windows 10 and on 32-bit Windows 7.
>
> Perhaps you donât need it, but part of the reason for the big push recently for reproducible builds is to be able to verify that binaries from a given source (e.g. Red Hatâs RPM feed) are in fact buildable from the sources distributed from the same source (e.g. Red Hatâs SRPMs).
Yes, that's a much more ambitious goal, and it's not what I was trying
to do.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-05-05 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 13:38 Ken Brown
2016-05-04 14:30 ` Greg Chicares
2016-05-04 17:11 ` Achim Gratz
2016-05-04 17:21 ` Ismail Donmez
2016-05-04 17:40 ` Ken Brown
2016-05-05 17:59 ` Ken Brown
2016-05-05 20:26 ` Warren Young
2016-05-05 21:46 ` Ken Brown [this message]
2016-05-05 1:50 ` Andrey Repin
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=466e1bc4-94b6-8eb7-0ea8-59680838e549@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).