Sure - but if 'module load icc' has gcc-4*' in path - that's a bug in the icc
module spec [as that version is incompatible with its c++ support] . It should
also load a compatible gcc version [via PATH - or via module dependencies]
if its implemented this way - then you won't have a broken icc
You say bug I say feature. Lmod has a way to mark modules as mutually
exclusive. That’s a decision of the way the site is set up. For most users
that’s a good idea.
For instance, if you load two compilers, and both have an MPI, how do you
decide which one is loaded by “load mpich”?
Etc. I’m
to be loaded at the same time.
>
> But yes, that would work.
>
> V.
>
> From: Satish Balay
> Date: Tuesday, August 8, 2023 at 11:20
> To: Victor Eijkhout
> Cc: Barry Smith , Khaled Nabil Shar Abdelaziz
> , petsc-users@mcs.anl.gov
> Subject: Re: [petsc-us
, August 8, 2023 at 11:20
To: Victor Eijkhout
Cc: Barry Smith , Khaled Nabil Shar Abdelaziz
, petsc-users@mcs.anl.gov
Subject: Re: [petsc-users] IMPI with Hypre
Its easier to just add the newer version of gcc/g++ compilers to PATH - and icc
will pick it up [without requiring -gcc-toolchain option
Its easier to just add the newer version of gcc/g++ compilers to PATH - and icc
will pick it up [without requiring -gcc-toolchain option]
export PATH=/location/of/newer/g++/bin:$PATH
./configure ...
make ...
Satish
On Tue, 8 Aug 2023, Victor Eijkhout wrote:
> Maybe an option for specifying
Maybe an option for specifying the explicit location of gcc version? The intel
compiler has a “-gcc-toolchain” option for that.
https://www.intel.com/content/www/us/en/docs/dpcpp-cpp-compiler/developer-guide-reference/2023-0/gcc-toolchain.html
Victor.
We get these reports regularly.
Intel is selecting [GCC 4.8.2 20140120 (Red Hat 4.8.2-15)] as the base
compiler, this ancient version does not provide the language support needed by
hypre. You need a more recent GNU compiler available for the Intel compilers to
base themselves on.
