From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, Nazir Bilal Yavuz <byavuz81@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: meson PGXS compatibility
Date: Wed, 05 Oct 2022 16:58:46 -0400
Message-ID: <2555941.1665003526@sss.pgh.pa.us> (raw)
In-Reply-To: <20221005204944.cwkaod6hfok2w7vj@awork3.anarazel.de>
References: <20221005200710.luvw5evhwf6clig6@awork3.anarazel.de>
<2551486.1665001222@sss.pgh.pa.us>
<20221005204944.cwkaod6hfok2w7vj@awork3.anarazel.de>
Andres Freund <andres@anarazel.de> writes:
> My understanding, from that commit message, was that the issue originates in
> apple's ranlib setting the timestamp to its components but only queries / sets
> it using second granularity. I verified that apple's ranlib and ar these days
> just set the current time, at a high granularity, as the mtime. Whether or
> not make then hides the problem seems not that relevant if the source of the
> problem is gone, no?
Well, (a) it seemed to happen in only some circumstances even back then,
so maybe your testing didn't catch it; and (b) even assuming that Apple
has fixed it in recent releases, there may still be people using older,
un-fixed versions. Why's it such a problem to keep the "touch" step?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, byavuz81@gmail.com, peter.eisentraut@enterprisedb.com
Subject: Re: meson PGXS compatibility
In-Reply-To: <2555941.1665003526@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox