Peter Scheibel

> which have the effect of automatically transliterating each variant val=var to envvar CHPL_VAL=var, while converting "spack" values to "system" (and "unset" to no setting) as expected by the Chapel...

> Does that satisfy your concern, Yes - thanks!

Does the following commit message seem reasonable? ``` * add cray detection taken from upcxx * add CUDA/ROCm support * add numerous pass-through options to Chapel build, like gpu_mem_strategy, comm_substrate,...

@alalazo recent updates: - Allow command-line `cflags=` override of propagation while allowing other flag sources (like `require:` and `depends_on`) to add to propagation - `FlagMap.intersects` and `FlagMap.constrain` are now consistent...

This has come up a couple times very recently (SDKs including implementations of packages) and I am considering an alternative approach: * The SDK package (`nvhpc`) can come with a...

> There are also libraries in the NVHPC SDK that are not in the CTK. @brycelelbach Could you mention an example? I also have a few other questions: * Is...

>> Could you mention an example? > NCCL, cuTENSOR. >> Is there a means to obtain the CUDA libraries other than via the CUDA toolkit or by the NVHPC SDK?...

>> cudart is an example of a library provided only in CTK. Unlike NCCL, I do not see a separate download option, so is it the case that the cudart...

Can you try using quotes: ``` spack_spec: "{default_comp} {sys_arch}" ``` I think the YAML parser is having trouble with `{}` in this case

This is a YAML issue, so not addressable by Spack/Ramble/Benchpark. Closing. Arguably re-open-able if one thinks a better error message would be ideal.