vim build tests require xz?

[Brian L. Matthews]

I build vim from source using:

./configure \
    --disable-gui \
    --enable-largefile \
    --enable-multibyte \
    --enable-python3interp \
    --prefix=/usr/local \
    --with-compiledby='Brian Matthews <blmatth...@gmail.com>' &&
    make &&
    make test

I did a git pull this morning, getting:

$ git rev-parse HEAD
8297e2cee337c626c6691e81b25e1f1897c71b86

The make and make test worked just fine on one machine. I then tried it
on my main development machine and it ended with:

01:58 Executing Test_glvs_default_tar_xz()
/bin/bash: unxz: command not found
tar: dumpx.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
mv: rename dumpx.tar to
/Users/blm/src/3rdparty/vim9/src/testdir/XfakeHOME/.vim/GetLatest/Installed/dumpx.tar:
No such file or directory

On the machine the build worked on:

01:20 Executing Test_glvs_default_tar_xz()
x dumpx/
x dumpx/README.md
x dumpx/LICENSE
x dumpx/plugin/
x dumpx/plugin/dumpx.vim
x dumpx/plugin/autoycm.pl
x dumpx/syntax/
x dumpx/syntax/dumpx.vim
x dumpx/doc/
x dumpx/doc/dumpx.txt

On the machine it fails:

$ type unxz
-bash: type: unxz: not found

And where it works:

$ type unxz
unxz is /usr/local/bin/unxz

I'm still on macOS Monterey, so maybe xz/unxz come standard with Xcode
for a newer macOS? Although I do an awful lot of development on a
machine with neither installed. :-)

There's an obvious workaround, although I kind of hate installing extra
stuff if I can avoid it, but thought someone would want to know.

Thanks,
Brian

[Christian Brabandt]

Thanks for reporting. Should be fixed with v9.1.1061

Thanks,
Christian
--
You will always find something in the last place you look.

[Brian L. Matthews]

On 1/31/25 8:04 AM, Christian Brabandt wrote:

Thanks for reporting. Should be fixed with v9.1.1061

It is! Builds, tests, and runs fine on both a machine with and without unxz. Thanks much Christian.

Brian