From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121994 invoked by alias); 5 May 2016 20:26:48 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 121982 invoked by uid 89); 5 May 2016 20:26:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=and, H*r:qmail-ldap-1.03, yum, H*i:sk:c69da50 X-HELO: etr-usa.com Received: from etr-usa.com (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 05 May 2016 20:26:37 +0000 Received: (qmail 27301 invoked by uid 13447); 5 May 2016 20:26:35 -0000 Received: from unknown (HELO polypore.west.etr-usa.com) ([73.26.17.49]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 May 2016 20:26:35 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Deterministic builds From: Warren Young In-Reply-To: Date: Thu, 05 May 2016 20:26:00 -0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <258af4b4-e1f0-171c-4b94-772603038fde@cornell.edu> To: The Cygwin Mailing List X-IsSubscribed: yes X-SW-Source: 2016-05/txt/msg00062.txt.bz2 On May 5, 2016, at 11:59 AM, Ken Brown wrote: >=20 > Ismail's suggestion did indeed produce deterministic builds in my setup. = I built a large project with about 150 executables, changed a few source f= iles, removed the build directory, rebuilt, and found that only the (expect= ed) few executables changed. =E2=80=A6and does it do the same on a very different system? e.g. Try it o= n both 64-bit Windows 10 and on 32-bit Windows 7. Perhaps you don=E2=80=99t 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=E2=80=99s RPM feed) are in fact buildable fro= m the sources distributed from the same source (e.g. Red Hat=E2=80=99s SRPM= s). The usual motivation for that is security: it=E2=80=99s no good receiving a= n SRPM with a security patch if the binary that yum installs still has the = bug. Therefore, if you get =E2=80=9Creproducible=E2=80=9D builds on only a singl= e machine, you may not have achieved any useful result. -- 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