DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=n5vGslaTafbjuscr
	1DPEN3lKS+Ek17+jBsnVXrARHpDFqOlLbKEplv+Ee1ZobJgtt0JyKeLOPL8ZWurK
	e0PW2q0c/v++ZRerFDEEJcUp/4KNpj4ABXFBLag/7mX8Csr+JXfPHij6VjpPa8w3
	Ng2SRhjcFgBlg1/gPRwOujtsqNQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Deterministic builds
To: cygwin@cygwin.com
References: <ff5f5b20-33e2-ef2d-012a-a9e02903ba21@cornell.edu>
From: Greg Chicares <gchicares@sbcglobal.net>
Message-ID: <572A0778.3080509@sbcglobal.net>
Date: Wed, 4 May 2016 14:30:16 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0
MIME-Version: 1.0
In-Reply-To: <ff5f5b20-33e2-ef2d-012a-a9e02903ba21@cornell.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2016-05-04 13:38, Ken Brown wrote:
> 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.)

'-fno-guess-branch-probability' removes one potential obstacle:
  https://lists.debian.org/debian-devel/2005/02/msg01154.html
I don't know if there are other obstacles than these.


--
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