Steps to reproduce
When spack finds an external gmake package in a macOS homebrew installation, it wants to use that one but can’t find /usr/local/bin/make (because homebrew leaves it as gmake). Poking around in the spack code I see that the spack install of gmake creates a symlink from gmake to make after installation, but of course it doesn’t do that for external packages.
I noticed that the concretizer output for an older (December 2022) spack doesn’t contain a gmake package at all, assuming therefore that spack always called make under the assumption that whatever is in the search path works? Meanwhile, the current spack version makes gmake an explicit dependence but then trips over the non-existent in /usr/local/bin/make.
Error message
Errors are therefore something like /usr/local/bin/make - no such file or directory
Information on your system
* **Spack:** 0.20.0.dev0 (ce81f15e6f7390953e0035ada5c0399da0c4e44b)
* **Python:** 3.10.8
* **Platform:** darwin-ventura-skylake
* **Concretizer:** clingo
General information
Steps to reproduce
When spack finds an external
gmakepackage in a macOS homebrew installation, it wants to use that one but can’t find/usr/local/bin/make(because homebrew leaves it asgmake). Poking around in the spack code I see that the spack install ofgmakecreates a symlink fromgmaketomakeafter installation, but of course it doesn’t do that for external packages.I noticed that the concretizer output for an older (December 2022) spack doesn’t contain a
gmakepackage at all, assuming therefore that spack always calledmakeunder the assumption that whatever is in the search path works? Meanwhile, the current spack version makesgmakean explicit dependence but then trips over the non-existent in/usr/local/bin/make.Error message
Errors are therefore something like
/usr/local/bin/make - no such file or directoryInformation on your system
General information
spack debug reportand reported the version of Spack/Python/Platform