Re: [easybuild] Packages lacking intel fortran runtime

Hi Alan, I tried making the changes in my intel/2018a modules, and it seemed to work exactly great. Though, now when I tried to build a new EB package, I get hit with some errors that toolchain definitions don't match. Adding icc and ifort back into the intel-module seems to have fixed it, so

Re: [easybuild] Packages lacking intel fortran runtime

Hi Mikael, On 12 April 2018 at 16:53, Mikael Öhman wrote: > Hi everyone, > > It seems to be that there is a consensus that moving the path extension to > iccifort would be the solution for the core issue here? > I.e. > 1. Move the path extension to iccifort > Yes, this is

Re: [easybuild] Packages lacking intel fortran runtime

Hi everyone, It seems to be that there is a consensus that moving the path extension to iccifort would be the solution for the core issue here? I.e. 1. Move the path extension to iccifort 2. Have the intel module load iccifort instead of icc and ifort independently I don't think hiding icc or

Re: [easybuild] Packages lacking intel fortran runtime

Sorry guys, I can't believe I didn't remember this (given that I wrote it) but our custom MNS fixes this problem: https://github.com/easybuilders/JSC/blob/master/Custom_MNS/2017b/custom_hierarchical_mns.py It ignores path extensions for icc/ifort (which are hidden for us anyway) and instead does

Re: [easybuild] Packages lacking intel fortran runtime

Yeah it is sorry, I was writing without checking! On 12 April 2018 at 15:44, Mikael Öhman > wrote: Hi Alan, However, I don't understand how you can run into this problem. Normally for any package the toolchain components are included as

Re: [easybuild] Packages lacking intel fortran runtime

Hi Alan, However, I don't understand how you can run into this problem. Normally for > any package the toolchain components are included as dependencies in the > final module: loading Caffe would also mean loading the missing ifort > module. I guess you must have a configuration that does not

Re: [easybuild] Packages lacking intel fortran runtime

Hej Joachim, We have the same issue. From the last EasyBuild user meeting, I got a few suggestions on how to try and fix the issue, but I was never successful with these. We try to educate out users to always use the toolchain packages whenever possible "module load intel". I think the nicest

Re: [easybuild] Packages lacking intel fortran runtime

Hi Joachim, We also have (a slightly customised) HMNS. For our users we hide the icc and ifort modules and only expose them to iccifort (which we rename to Intel using a custom naming scheme). This is one way to get around your issue. However, I don't understand how you can run into this

RE: [easybuild] Packages lacking intel fortran runtime

Hi Joachim! Yes, we have encountered the same issue you described before. Our way of dealing with it is to expose to the users only the iccifort toolchain module, while icc and ifort are hidden. Definitely not the most elegant solution if you still want to let the users select icc or ifort