This is the mail archive of the
mailing list for the Cygwin project.
Re: Deterministic builds
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Wed, 04 May 2016 19:11:20 +0200
- Subject: Re: Deterministic builds
- Authentication-results: sourceware.org; auth=none
- References: <ff5f5b20-33e2-ef2d-012a-a9e02903ba21 at cornell dot edu>
Ken Brown writes:
> Is it possible to build an executable on Cygwin so that subsequent
> builds (with no change in source) produce identical results?
> Currently, the timestamp embedded in executables prevents this. (I
> don't know if that's the only obstacle.)
I think the basic problems and solutions could be sussed from the work
of Debian folks on reproducible builds:
> 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.
Just looking at executables, you will probably find that in gcc there
are a few optimizations that do not produce the same bits on each
compile (depending on available memory, CPU speed or some random seed).
For some of these there are switches to stabilize the result at least.
Timestamps in various file formats are another source of chatter,
although you might be able to either fix thetime or just ignore those
timestamps during comparison (but that's generally more costly than just
doing a plain comparison).
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple