From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Add initial support for SOURCE_DATE_EPOCH
Date: Tue, 29 Aug 2023 10:52:32 +0200 [thread overview]
Message-ID: <ef7c2903-ce3d-7884-0f1f-c49600380f07@t-online.de> (raw)
In-Reply-To: <874jkjtbb4.fsf@Otto.invalid>
ASSI via Cygwin-apps wrote:
> Christian Franke via Cygwin-apps writes:
>> If the build-path changes, more files differ (cygcheck.exe, ldd.exe,
>> cygserver.exe) because __FILE__ is used and expands to an absolute
>> path name.
> This could be fixed by adding -fmacro-prefix and/or -ffile-prefix arguments.
Yes, -fmacro-prefix-map should do the trick.
Meantime I found a workaround for the additional timestamp in the PE
Export Tables header:
The ld option --no-insert-timestamp also sets this timestamp to 0. This
is apparently preserved by objcopy, regardless of --preserve-dates option.
--
Regards,
Christian
next prev parent reply other threads:[~2023-08-29 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 17:39 Christian Franke
2023-08-24 2:45 ` Brian Inglis
2023-08-24 6:09 ` Christian Franke
2023-08-24 6:27 ` ASSI
2023-08-24 6:36 ` Christian Franke
2023-08-28 15:12 ` Christian Franke
2023-08-28 15:51 ` ASSI
2023-08-29 8:52 ` Christian Franke [this message]
2023-10-29 16:05 ` Jon Turney
2023-10-30 17:43 ` 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=ef7c2903-ce3d-7884-0f1f-c49600380f07@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin-apps@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).