#215 uses ~bootstrap to disambiguate compilers from different sources. If stack-config is run twice on the same build directory, ~bootstrap gets added twice to the compiler spec and spack errors out, because ~bootstrap ~bootstrap isn't allowed:
spack -e gcc/ concretize -f
==> Error: Cannot specify variant "bootstrap" twice
gcc@12.4.0 languages:='c,c++' ~bootstrap ~bootstrap
If the custom compiler bootstrapping is removed completely this is a non-issue. Otherwise we just need to check that we don't add ~bootstrap twice.
This should not be a blocker for using #215, but does require starting with a clean build directory every time stack-config is used.
#215 uses
~bootstrapto disambiguate compilers from different sources. Ifstack-configis run twice on the same build directory,~bootstrapgets added twice to the compiler spec and spack errors out, because~bootstrap ~bootstrapisn't allowed:If the custom compiler bootstrapping is removed completely this is a non-issue. Otherwise we just need to check that we don't add
~bootstraptwice.This should not be a blocker for using #215, but does require starting with a clean build directory every time
stack-configis used.