On 16 Oct 2013, at 15:36, Jure Pečar wrote: > On Wed, 16 Oct 2013 11:48:17 +0200 > Kenneth Hoste <[email protected]> wrote: > >> WIth the current EasyBuild version, I highly recommend you to reinstall icc >> & co in an install path controlled by EasyBuild... >> >> I understand that you want to avoid having multiple copies around, and to >> have your setup Intel complaint, but EasyBuild does not easily allow this >> currently. >> >> Getting everything tweaked such that EasyBuild is happy to use what you >> already have can be done, but requires you to be familiar with EasyBuild's >> guts and will be very time-consuming. > > Possibly, but at least for Intel stuff I can manage.
Is "A warned man is worth two men" a world-wide idiom? ;-) Again, I can see where the desire comes from to simply make EasyBuild use what is there already in some way. To be more specific what is missing in your case: the easyblock for Intel MKL builds FFTW wrapper interfaces, that are not installed by default. >From your original message, it seems like that's exactly what's missing in >your /opt/intel installation. See post_install_step in https://github.com/hpcugent/easybuild-easyblocks/blob/master/easybuild/easyblocks/i/imkl.py for how this is taken care of by EasyBuild. Be aware that you'll have to make sure the FFTW wrappers are made available every time you update the stack in /opt/intel, and that EasyBuild expects that icc, ifort. impi, imkl installs never disappear... If stuff disappears, software that was built on top of it may breaks because paths change, libraries are no longer there (with the same naming as before), etc. That being said: if you manage to get it to work, please share any documentation you may have on the procedure... > >> We can try and help to make future versions of EasyBuild able to set up an >> Intel complaint system (any reference for what that requires), but for now >> just going EasyBuild all the way is definitely your best option. > > http://software.intel.com/sites/default/files/Intel_Cluster_Ready_Specification_1.3_Final.pdf > >> Quick thought: is symlinking /opt/intel to the EasyBuild install locations >> an option at all? > > That could be doable if both /opt and eb install_path (like /usr/local) are > exported to all nodes. Which of both would not be exported to all nodes? Do you have dedicated build nodes, which would only have /opt/intel available? How do you handle dynamic linking of libraries, etc. in that case? regards, Kenneth
