From c6ee30497c59d19d78a9ccf48ce54fb7430818d3 Mon Sep 17 00:00:00 2001 From: Cristian Le Date: Tue, 29 Nov 2022 13:45:28 +0100 Subject: Fix libxc cflag (#34000) Using standard c99 should not be specific to intel compilers. --- var/spack/repos/builtin/packages/libxc/package.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'var') diff --git a/var/spack/repos/builtin/packages/libxc/package.py b/var/spack/repos/builtin/packages/libxc/package.py index 4ee0c3e4ef..0b1ec27b98 100644 --- a/var/spack/repos/builtin/packages/libxc/package.py +++ b/var/spack/repos/builtin/packages/libxc/package.py @@ -73,8 +73,10 @@ class Libxc(AutotoolsPackage, CudaPackage): # by Spack, otherwise we may end up with contradictory or invalid flags # see https://github.com/spack/spack/issues/17794 + # https://gitlab.com/libxc/libxc/-/issues/430 (configure script does not ensure C99) + # TODO: Switch to cmake since this is better supported + env.append_flags("CFLAGS", self.compiler.c99_flag) if "%intel" in self.spec: - env.append_flags("CFLAGS", "-std=c99") if which("xiar"): env.set("AR", "xiar") -- cgit v1.2.3-70-g09d2