From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>,
Christian Franke <Christian.Franke@t-online.de>
Subject: Re: [PATCH] Add initial support for SOURCE_DATE_EPOCH
Date: Sun, 10 Sep 2023 15:41:35 +0100 [thread overview]
Message-ID: <a691f19e-ec1b-3b5e-7495-77156799dbd0@dronecode.org.uk> (raw)
In-Reply-To: <ZPsrFKgcmt2qrH34@calimero.vinschen.de>
On 08/09/2023 15:09, Corinna Vinschen wrote:
> Jon,
>
> you did all the latest work in terms of the build machinery.
> Would you mind to review this patch, please?
Sure.
Patch looks all right to me, so I applied it.
> On Sep 5 19:01, Christian Franke wrote:
>> This patch enables reproducible builds of cygwin package in conjunction with
>> this cygport patch:
>> https://sourceware.org/pipermail/cygwin-apps/2023-August/043108.html
>>
>> cygwin.cygport was enhanced for the test as described in the above post.
>>
>> If the same build path, SOURCE_DATE_EPOCH and toolchain are used, rebuilds
>> with cygport produce identical distribution tarballs. Adding proper
>> -fmacro-prefix-map gcc options (or remove all usages of __FILE__) could
>> possibly make this independent from the build path.
>>
>> Note that 'u' (replace with newer objects only) flag needed to be removed
>> from ar commands because it is incompatible with 'D' (deterministic
>> archive). I don't expect any negative effect because existing .a files are
>> always removed before ar is run.
>>
>> Not yet tested with different machines or different users accounts.
>>
>> Patch would be much simpler (mkvers.sh only) if binutils would support
>> SOURCE_DATE_EPOCH directly.
>>
next prev parent reply other threads:[~2023-09-10 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 17:01 Christian Franke
2023-09-08 14:09 ` Corinna Vinschen
2023-09-10 14:41 ` Jon Turney [this message]
2023-09-10 17:32 ` Christian Franke
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=a691f19e-ec1b-3b5e-7495-77156799dbd0@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Christian.Franke@t-online.de \
--cc=cygwin-patches@cygwin.com \
/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).