We are investigating spack environments as a way to replicate build environments and noticed top level dependencies being built as separate variants.
Is this expected behavior or should the concretization process be spread across all specs in the spack.yaml?
Steps to reproduce the issue
Reproduced on multiple platforms and verified in the spack/ubuntu:18.04 container with commit 7a28a61
[ubuntu] tmp2: cat spack.yaml
spack:
specs:
- boost@1.68.0
- trilinos@12.12.1
Error Message
[ubuntu] tmp2: spack concretize -f
==> Concretizing boost@1.68.0
- 7znc464 boost@1.68.0%gcc@7.3.0+atomic+chrono~clanglibcpp cxxstd=default +date_time~debug+exception+filesystem+graph~icu+iostreams+locale+log+math~mpi+multithreaded~numpy patches=2ab6c72d03dec6a4ae20220a9dfd5c8c572c5294252155b85c6874d97c323199 ~pic+program_options~python+random+regex+serialization+shared+signals~singlethreaded+system~taggedlayout+test+thread+timer~versionedlayout+wave arch=linux-ubuntu18.04-x86_64
...
==> Concretizing trilinos@12.12.1
- kmmhk7k trilinos@12.12.1%gcc@7.3.0~alloptpkgs+amesos+amesos2+anasazi+aztec+belos+boost build_type=RelWithDebInfo ~cgns~complex~debug~dtk+epetra+epetraext+exodus+explicit_template_instantiation~float+fortran~fortrilinos+gtest+hdf5+hypre+ifpack+ifpack2~intrepid~intrepid2~isorropia+kokkos+metis~minitensor+ml+muelu+mumps~nox~openmp~phalanx~piro~pnetcdf~python~rol~rythmos+sacado~shards+shared~stk+suite-sparse~superlu~superlu-dist~teko~tempus+teuchos+tpetra~x11~xsdkflags~zlib+zoltan+zoltan2 arch=linux-ubuntu18.04-x86_64
- tumf2uc ^boost@1.69.0%gcc@7.3.0+atomic+chrono~clanglibcpp cxxstd=default +date_time~debug+exception+filesystem+graph~icu+iostreams+locale+log+math~mpi+multithreaded~numpy patches=2ab6c72d03dec6a4ae20220a9dfd5c8c572c5294252155b85c6874d97c323199 ~pic+program_options~python+random+regex+serialization+shared+signals~singlethreaded+system~taggedlayout+test+thread+timer~versionedlayout+wave arch=linux-ubuntu18.04-x86_64
We are investigating spack environments as a way to replicate build environments and noticed top level dependencies being built as separate variants.
Is this expected behavior or should the concretization process be spread across all specs in the spack.yaml?
Steps to reproduce the issue
Reproduced on multiple platforms and verified in the spack/ubuntu:18.04 container with commit 7a28a61
Error Message