Installation issue: windows: nasm installs an empty directory #29575
Description
Steps to reproduce the issue
$ spack install nasm
==> [2022-03-17-15:31:17.568821] No binary for nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntax found: installing from source
==> [2022-03-17-15:31:17.568821] Creating the installation directory C:\Users\trws\Repos\spack-clean\opt\spack\windows-windows10-AMD64\msvc-19.31.31104\nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntax
==> [2022-03-17-15:31:17.572829] 'C:\Program' 'Files\Git\cmd\git.exe' 'describe' '--tags' '--match' 'v*'
==> Using cached archive: C:\Users\trws\Repos\spack-clean\var\spack\cache\_source-cache\archive\91\9182a118244b058651c576baa9d0366ee05983c4d4ae1d9ddd3236a9f2304997.tar.gz
←[1;34m==>←[0m Applied patch C:\Users\trws\Repos\spack-clean\var\spack\repos\builtin\packages\nasm\msvc.mak.patch
←[1;34m==>←[0m Ran patch() for nasm
←[1;34m==>←[0m nasm: Successfully installed nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntax
Fetch: 0.00s. Build: 10.47s. Total: 10.48s.
←[1;32m[+]←[0m C:\Users\trws\Repos\spack-clean\opt\spack\windows-windows10-AMD64\msvc-19.31.31104\nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntax
←[0;32m==>←[0m [2022-03-17-15:31:30.888768] Flagging nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntax as installed
←[0;32m==>←[0m [2022-03-17-15:31:30.888768] Downgrading to a read lock on nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntax with timeout 1e-09
←[0;32m==>←[0m [2022-03-17-15:31:30.888768] nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntax is now read locked
←[0;32m==>←[0m [2022-03-17-15:31:30.888768] Releasing read lock on nasm-2.15.05-z5j6is2g4fpzt2atd7qwj42iic3dntaxError message
Error message
No error message, but also no nasm.exe
Information on your system
- Spack: 0.17.1-1606-5a72204d38
- Python: 3.9.5
- Platform: windows-windows10-AMD64
- Concretizer: original
Additional information
spack-build-out.txt
spack-build-env.txt
General information
- I have run
spack debug reportand reported the version of Spack/Python/Platform - I have run
spack maintainers <name-of-the-package>and @mentioned any maintainers - I have uploaded the build log and environment files
- I have searched the issues of this repo and believe this is not a duplicate