Create option to build compilers as needed #10761
Conversation
…e installing packages that use them
becker33
force-pushed
the
features/install-compilers-as-needed
branch
from
f6c60b2
to
e85d486
Compare
becker33
force-pushed
the
features/install-compilers-as-needed
branch
from
f82a570
to
68945c7
Compare
becker33
force-pushed
the
features/install-compilers-as-needed
branch
from
68945c7
to
ddb3513
Compare
|
@scheibelp addressed all comments. |
|
Related PR #7868 |
Is there any way to decide which spec will be used to build a compiler, or will it always be the default one? |
|
@alalazo if you specify a compiler, it will use that compiler and version, and concretize the rest using the package preferences from packages.yaml. If you don't specify a compiler, or if there is a compiler that satisfies your abstract spec, then you'll still get the compiler that is already on the system. |
Thanks, that's the bit I was missing - I guess I am just not used to customize |
Compilers are treated separately from other dependencies in Spack. #10761 added the option to automatically install compilers when a package specifies using a compiler that is not available in Spack. However, this did not work correctly for dependency packages (it would only build a compiler for the root of an install DAG). This commit enables the building of compilers for dependency packages.
This PR adds a config option that allows concretization to match to compilers that are not already available, and changes the install logic to build the compiler and add it to the configuration at install time of the package building against that compiler.
The option is controlled by the
install_missing_compilersboolean flag in theconfig.yamlconfiguration file.Currently, if no compiler
gcc@7.3.0is available on the system,spack install zlib%gcc@7.3.0will raise a concretization error. With this PR and when the option is turned on,spack install zlib%gcc@7.3.0will build gcc and all its dependencies (with a default compiler) before building zlib against that gcc install.