Dear André,

If you want to contribute easyconfigs, it's entirely up to you which toolchain you use. Generally it's a good idea to just open a pull request for the toolchain that you are actually using (mainly to avoid you spending time to deal with potential problems when switching to another toolchain). The intel/2018a is the latest version of one of the "common" toolchains (the other one being foss/2018a), which means it's used quite commonly in the community, but that doesn't imply that easyconfigs using intel/2018.02 are not useful.

W.r.t. upgrading the compiler version in intel/2018a: we don't change the toolchain definitions once they have been fixed, but review the common toolchains every 6 months. Of course bugs are going to pop up over time, but that'll be the case with any compiler version we use.

In a couple of weeks we will be looking to define the 2018b update of the common toolchains, and intel/2018.02 is going to be a good candidate there, since it contains the latest (stable) version of icc/ifort/impi/imkl currently available.


regards,

Kenneth

On 16/05/2018 14:58, André Gemünd wrote:
Dear EasyBuilders,

please let me add to that.

Coincidentally, there is a bug in the compiler version of Intel 2018a that lets 
the compiler segfault during compilation of MUMPS: 
https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/754459

Wouldn't it make sense to have the upgrade be used in the 2018a toolchain?

Greetings
André

----- Am 16. Mai 2018 um 10:27 schrieb Andre Gemuend 
[email protected]:

Dear List,

I apologize upfront if this question has been asked multiple times before (I
feel I have seen it, but don't find it anymore).

We're currently preparing a few recipes and would like to use Intel 2018.2,
meaning icc/icpc/ifort 18.0.2 and mpi 2018.2.199 instead of version 1 thats in
intel-2018a. To give back something, I was thinking of submitting them for the
first time (yay), but wonder if it makes sense to specify as toolchain intel
2018.02 then, or if I should instead use 2018a? This still somehow baffles me.
We like to have most things build with the latest compilers. Hope someone can
shed some light on this for me.

Best Greetings
--
André Gemünd
Fraunhofer-Institute for Algorithms and Scientific Computing
[email protected]
Tel: +49 2241 14-2193
/C=DE/O=Fraunhofer/OU=SCAI/OU=People/CN=Andre Gemuend

Reply via email to