On 2026-10-31 11:05, Brian Inglis via tz wrote:
it would be better never to clear the directory contents, except at the start
or end of the whole build, rather than within that stage.
Unfortunately that would break "make now.ck" when run from the command line. "make
now.ck" needs that directory to be pristine, which it might not be if a previous "make" was
interrupted.
If you don't want files to be removed, you can prepend to your PATH a directory
containing an 'rm' program that does nothing.
Here are some ideas for speeding things up. I don't use Cygwin so am just
guessing to some extent:
* Set LC_ALL="C" in your environment.
* Exclude the Cygwin root from antivirus scanners like Windows Defender.
* Keep Active Directory out of the loop when checking file permissions. E.g.,
run cygserver on login.
I am talking about building packages for distros, where we are building
straight from a previously cached downloaded tarball, and not changing anything.
In that case, running "make check" the second time (without doing any changes)
should be fast even on an old machine, because there's no reason to run zdump or awk or
anything like that. All the second 'make' needs to do is look at file timestamps. It
should behave like this:
$ make check
make: Nothing to be done for 'check'.
If it doesn't work that way, I would suspect your filesystem is mishandling
file timestamps somehow.
I have an oldish AMD APU running Cygwin builds on rusty drives.
What is the CPU model number? How much RAM? How does its speed compare to the
following transcript on my old slow machine (a circa 2001 750 MHz UltraSPARC
III with 2 GiB RAM, running Solaris 10, with slow access to files via NFS)?
$ make clean >/dev/null 2>&1
$ time cp README README-copy
real 0m0.061s
user 0m0.004s
sys 0m0.011s
$ time awk 'BEGIN{for (i=0; i < 100000; i++) a[i] = i;}'
real 0m26.912s
user 0m26.459s
sys 0m0.148s
$ time make CFLAGS='-DHAVE_STRNLEN=0' >/dev/null 2>&1
real 0m31.850s
user 0m25.911s
sys 0m3.762s
$ time make check >/dev/null 2>&1; echo status is $?
real 10m46.585s
user 7m8.582s
sys 0m16.116s
status is 0
$ echo $PATH
/r/share1/src/developerstudio12.6/bin:/usr/xpg4/bin:/usr/bin
I would try to look at building the zone list and `zdump` all once thru `sed`
to cleanup directly into the consolidated output file.
That's already done in the now.ck rule whose output you quoted in your first
email. That rule calls zdump just twice, once to create zdump-now.tab and once
to create zdump-1970.tab. It then uses awk to analyze zdump-now.tab.