From: Andrey Repin <anrdaemon@yandex.ru>
To: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: Deterministic builds
Date: Thu, 05 May 2016 01:50:00 -0000 [thread overview]
Message-ID: <139590677.20160505043725@yandex.ru> (raw)
In-Reply-To: <ff5f5b20-33e2-ef2d-012a-a9e02903ba21@cornell.edu>
Greetings, Ken Brown!
> Is it possible to build an executable on Cygwin so that subsequent
> builds (with no change in source) produce identical results?
General answer is "no". It is possible to build a consistent object binary,
but executable linked from it will be different on different systems, for
various reasons.
> Currently,
> the timestamp embedded in executables prevents this. (I don't know if
> that's the only obstacle.)
Timestamps are the least of your issues.
Think of things like stack allocation bases.
> My actual use case is that I'm building a package that produces a large
> number of executables. If I make a change in one source file, I'd like
> to be able to know which executables change.
If your interest is purely self-educational, you can limit the noise on a
particular given system. But I wouldn't try to make any universal claims if I
were you.
--
With best regards,
Andrey Repin
Thursday, May 5, 2016 04:32:14
Sorry for my terrible english...
--
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
prev parent reply other threads:[~2016-05-05 1:50 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
2016-05-05 1:50 ` Andrey Repin [this message]
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=139590677.20160505043725@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).