Hi Jure, On 16 Oct 2013, at 11:40, Jure Pečar wrote:
> On Tue, 15 Oct 2013 15:39:40 +0200 > Kenneth Hoste <[email protected]> wrote: > >> Hold on... Are you saying you just unpacked the tarball, or installed Intel >> MKL from that tarball yourself, as opposed to letting EasyBuild install MKL? >> >> That's not going to work, EasyBuild does more than just install Intel MKL, >> it also builds the FFT wrappers (which is exactly what you're missing) >> according to the original error message. > > Yes, that was my whole idea. To get modulefiles written in a way for > EasyBuild to use existing icc&co installation. > >> Any reason why you're not using EasyBuild to install imkl? > > My first priority is to have "Intel Cluster Ready" compliant system. That > requires icc&co to be installed in /opt/intel. I want EasyBuild to drop > everything in /usr/local and would like to avoid having two icc installations > on the system. > > I'll look now into what else EB does with mkl and how to make it happy. 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. 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. Quick thought: is symlinking /opt/intel to the EasyBuild install locations an option at all? regards, Kenneth
