On 2026-10-30 17:01, Brian Inglis via tz wrote:
Many distros have build and check policies that they *MUST* work without any 
network access

To do that, use "make CURL=: check" as documented in the Makefile. That should suffice 
when building from a release tarball. Although building from Git typically does need network access 
to fetch the Git repository and leap-seconds.list, after that CURL=":" should suffice 
there, too.

make DATAFORM=rearguard EXPIRES_LINE=1 PACKRATDATA=backzone PACKRATLIST= REDO=posix_right VERSION_DEPS= -ik check

That command uses make's -i option, which does not work with TZDB's Makefile. Generally speaking, 
"-i" is not a good idea unless a Makefile is specifically written with "-i" in 
mind.

Omitting "-i" should fix the problem with "rm -fr" that you mentioned, because when the previous 
command in that recipe fails, "make" will not go on to execute "rm -fr".

or depending on some change of the upstream sources, or moved into the main 
build process, or to a maintainer rule, otherwise everything is redone if there 
is any issue during or after that stage

Tests are redone if dependencies change, and by default all tests depend on pretty much 
every source file. You can work around some of this by using "make VERSION=unknown 
VERSION_DEPS="; although this may cause the version info to be wrong, it should 
avoid redoing some tests if you change just a few files and don't care about version 
mismatches.

taking 15 minutes just for the zdumps.

It shouldn't take that long even on a slow CPU. Are you compiling without 
optimization? If so, try using -O2 or something like that. If that doesn't 
help, please use profiling to see why zdump is so slow, as it shouldn't be. 
Even the oldest, slowest machine I have ready access to (a circa 2001 750 MHz 
UltraSPARC III and with slow access to files via NFS) is several times faster 
than what you describe.
PS. In release 2026f, EXPIRES_LINE=1 was deprecated, and we plan to remove it 
in a future release because leap second tables are now frozen indefinitely.

Reply via email to