Installation issue: rust installation missing files or directories (?)

[dipietrantonio]

Steps to reproduce the issue

I have tried to build the following Rust code, https://github.com/MWATelescope/mwalib, using Cargo from rust@1.76.0. Rust was built and installed via spack 0.19 using the spack 0.22 recipe with minor syntax modifications (removed the maintainer clause). Unfortunately the Cargo build process ends with the error shown below. The same mwalib software builds without issues using a rust installation through rustup. I wonder whether differences in the installation trees cause the issue.

Thank you for your help

Error message

Error message

error: failed to run custom build command for `mwalib v1.3.2 (/scratch/pawsey1045/cdipietrantonio/setonix/2023.08/software/cdipietrantonio/build_stage/spack-stage-mwalib-1.3.2-s56ktjm3ojcgjfnywikmnlckehsqxzxy/spack-src)`

Caused by:
  process didn't exit successfully: `/scratch/pawsey1045/cdipietrantonio/setonix/2023.08/software/cdipietrantonio/build_stage/spack-stage-mwalib-1.3.2-s56ktjm3ojcgjfnywikmnlckehsqxzxy/spack-src/target/release/build/mwalib-d346c992f8eb7e1e/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at build.rs:22:31:
  Failed to acquire build-time information: Os { code: 2, kind: NotFound, message: "No such file or directory" }

Information on your system

spack debug report

• Spack: 0.19.0
• Python: 3.10.10
• Platform: linux-sles15-zen3
• Concretizer: clingo

maintainer @alecbcs

Additional information

I believe those two files won't provide useful information in this case.

General information

• I have run spack debug report and 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

[alecbcs]

@dipietrantonio can you try installing using a temporary download of spack@develop and see if you get the same result? (Make sure to backup/move your existing ~/.spack directory prior to running the newer version of Spack.)

[dipietrantonio]

Hi @alecbcs I confirm this happens with spack/develop too. Same error message.