spack: cmake install on Mac OS 10.13.4 using intel@18.0.2 fails
Summary I tried to install pfunit using spack on my Mac Pro workstation using the intel 18.0.2 compiler. The installation failed when the dependency for cmake was attempted to be installed. The error was the the intel C++ compiler did not support C++11, which is false. By default this compiler enables the C++11 standard via the command line -std=c++11. The build script for cmake did not know enough about the Intel compiler to automatically add this argument. I probably could work around this problem, but it should have been handled transparently by me. In fact this issue brings up the general question of why spack thought it needed to install cmake in the first place since I already had a working version in my path via macports. I probably could also have added one via spack using clang@9.1.0. This seems to be a general issue with spack. When it needs a executable tool it just blindly installs one, without first checking whether it was really needed. I assume this has something to do with the “build clean” philosophy spack uses since it probably clobbers the executable path as well as the rest of the environment.
Expected Result
Spack would do correctly what I requested and be smart enough to know about compiler options and executable tools.
Actual Result
The installation failed for the reasons described above.
Steps to reproduce the issue
I ran “spack install pfunit %intel@18.0.2” but the problem should be reproduced by “spack install cmake %intel@18.0.2”
Incidentally, the installation use gnu@7.3.0 for cmake failed due to incompatibilities with the CoreGraphics framework on my mac and the installation for pfunit using clang also fails since the git site https://git.code.sf.net/p/pfunit/code was unavailable. Could this address be obsolete?
Information on your system
Mac Pro late 2013 model running OS 10.13.4. I have the gnu compilers via spack and purchased licenses for the intel compilers, current version 18.0.2.
We encourage you to try, as much as possible, to reduce your problem to the minimal example that still reproduces the issue. That would help us a lot in fixing it quickly and effectively!
If you want to ask a question about the tool (how to use it, what it can currently do, etc.), try the #general channel on our Slack first. We have a welcoming community and chances are you’ll get your reply faster and without opening an issue.
Other than that, thanks for taking the time to contribute to Spack!
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 15 (9 by maintainers)
@adamjstewart Cool, thanks. I’ll keep the version in. Just never thought about that until now.
I have an example
packages.yamlfor MacOS here you can start with. You can put it inspack/etc/spackor~/.spackand it will read it. https://github.com/Exawind/build-test/blob/master/configs/machines/mac_high_sierra/packages.yaml