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 - that requires a swap of gcc. Satish On Tue, 8 Aug 2023, Victor Eijkhout wrote: > 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 sure thought has gone into this. > > Victor. > > > << >
