[bug#61240] improve high-res file timestamp in Automake

2023-02-05 Thread Paul Eggert
On 2023-02-05 21:43, Jacob Bachmeyer wrote: Should the patch be relative to commit 6d6fc91c472fd84bd71a1b012fa9ab77bd94efea (before the version requirement bump) or should it include reverting commit 4e3744a15c4d8bdb46c11ead2fb56c5f591b714b (the version requirement bump)? Might as well do i

[bug#61240] improve high-res file timestamp in Automake

2023-02-05 Thread Jacob Bachmeyer
Paul Eggert wrote: On 2023-02-05 17:14, Jacob Bachmeyer wrote: [...] Looking at the code, commit 01bf65daf6f6627b56fbe78fc436fd877ccd3537 appears fine, all I am asking is that commit 4e3744a15c4d8bdb46c11ead2fb56c5f591b714b be reverted. The current Automake Git master should actually work on

[bug#61240] improve high-res file timestamp in Automake

2023-02-05 Thread Paul Eggert
On 2023-02-05 17:14, Jacob Bachmeyer wrote: How often is Perl built to use long doubles these days?  (That was an option beginning with Perl 5.6.) I doubt it's used much. It's not used in Ubuntu or Fedora, for what it's worth. And on some platforms (e.g., macOS on current Apple silicon) -Dus

[bug#61240] improve high-res file timestamp in Automake

2023-02-05 Thread Jacob Bachmeyer
Paul Eggert wrote: On 2023-02-04 16:02, Jacob Bachmeyer wrote: In any case, you will still need to account for the possibility that Time::HiRes::stat() might not actually have higher resolution, depending on the filesystem. That's fine. All we want is the exact file timestamp. If the file sy