On 2025-12-19 19:27, Paul Eggert wrote:
On 2025-12-19 15:42, Brian Inglis via tz wrote:
The attached logs show the results of having the package build scripts run
`make check` from the package build directory which is set up with symlinks to
each of the tar sources.
Is there anything obviously missing or incorrect with `make check` invocations
The 'make check' rule checks all of tzdb, both code and data. In those logs it
fails in a tzcode-only build because some data files are missing, and it fails
in a tzdata-only build because some code files are missing.
One fix would be to get both code and data into the same directory, do a 'make
check' there, and then use that directory to generate the programs and/or data
that you need (possibly as separate Cygwin packages).
For checking, I create symlinks to /dev/null for files missing from
VERSION_DEPS, and make -k check now seems to be working mostly normally with
both tar sources, except tzdata is trying to rebuild executables, rather than
using the installed release.
Copying from /usr/*bin/ does not work. Any suggestions for an adequate bypass?
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
