This is the mail archive of the
mailing list for the Cygwin project.
Re: Deterministic builds
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Ken Brown <kbrown at cornell dot edu>, cygwin at cygwin dot com
- Date: Thu, 5 May 2016 04:37:25 +0300
- Subject: Re: Deterministic builds
- Authentication-results: sourceware.org; auth=none
- References: <ff5f5b20-33e2-ef2d-012a-a9e02903ba21 at cornell dot edu>
- Reply-to: cygwin at cygwin dot com
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
> 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
With best regards,
Thursday, May 5, 2016 04:32:14
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple