From e76462da3874085d35ffa3c4e71858423dedc695 Mon Sep 17 00:00:00 2001 From: Harmen Stoppels Date: Sun, 26 Sep 2021 12:28:30 +0200 Subject: Compiler conflict in umpire as a range (#26161) --- var/spack/repos/builtin/packages/umpire/package.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'var') diff --git a/var/spack/repos/builtin/packages/umpire/package.py b/var/spack/repos/builtin/packages/umpire/package.py index b600863c29..9580438b3c 100644 --- a/var/spack/repos/builtin/packages/umpire/package.py +++ b/var/spack/repos/builtin/packages/umpire/package.py @@ -103,7 +103,10 @@ class Umpire(CachedCMakePackage, CudaPackage, ROCmPackage): conflicts('+shared', when='+cuda') # https://github.com/LLNL/Umpire/issues/653 - conflicts('%gcc@10.3.0', when='+cuda') + # This range looks weird, but it ensures the concretizer looks at it as a + # range, not as a concrete version, so that it also matches compilers + # specified as `gcc@10.3.0-identifier`. See #8957. + conflicts('%gcc@10.3.0:10.3.0.0', when='+cuda') def _get_sys_type(self, spec): sys_type = spec.architecture -- cgit v1.2.3-70-g09d2