Hello, > On 21 Feb 2014, at 20:32, [email protected] wrote: > > I have recently acquired a position as an intern at a university and they want > me to compare easy build to regular methods of module building.
What are the other methods? Manual builds and module file creation? Or something else? > I have > successfully built openmpi as well as mpich using easy build, but only by > using dummy for the toolchain name and version. Firstly, whenever I try to > specify a specific toolchain, I have problems. Secondly, I don't quite > understand how to input something like intel v14.0 as my toolchain, because of > course it doesn't exist. > > So here is my log from trying to build mpich using iccifort v2011.13.367: > > == temporary log file in case of crash /tmp/easybuild-i84Cpy/easybuild- > U6PLRp.log > == resolving dependencies ... > == processing EasyBuild easyconfig /afs/crc.nd.edu/user/k/khostetl/testThings/ > configureTest/easybuild-1.10.0/lib/python2.7/site-packages/ > easybuild_easyconfigs-1.10.0.0-py2.7.egg/easybuild/easyconfigs/i/icc/ > icc-2011.13.367.eb > == building and installing icc/2011.13.367... > == fetching files... > ERROR: EasyBuild encountered an exception (at easybuild/main.py:809 in > build_and_install_software): autoBuild Failed (last 300 chars): easyconfigs/ > l_ccompxe_2011.13.367.tgz, /afs/crc.nd.edu/user/k/khostetl/.local/easybuild/ > sources/i/icc/l_ccompxe_2011.13.367.tgz, /afs/crc.nd.edu/user/k/ > khostetl/.local/easybuild/sources/icc/l_ccompxe_2011.13.367.tgz, /afs/ > crc.nd.edu/user/k/khostetl/.local/easybuild/sources/l_ccompxe_2011.13.367.tgz > > Actually, before I started using --robot, this same file would fail on > resolving dependencies. It would say dependencies not met, when iccifort is a > default toolchain. --robot has remedied that, but only to bring me to this new > "fetching files" fail problem. The fact that it fails without --robot is normal, robot enables the dependency resolution. Without robot, the modules for the dependencies have to be there (from an earlier EB run), then it won't complain... Since the iccifort toolchain is not there yet, EB will install that first. The first part is the Intel C compiler, icc. But, EasyBuild can't download the required installation files for you (the Intel tools are licensed, and you need to log in to download them). So, for icc, ifort, etc, download them yourself and put them somewhere where EB will look for it (by default, $HOME/.local/easybuild/sources/i/icc, etc). > The best answer I could get to my problem would be an explanation on how I can > use a particular intel version (eg. 12.1, 14.0, etc.) or pgi, or gcc, etc. The 2011.x is the 'version' under which the tools are released, which is different from what e.g. 'icc --version' actually prints. We have heard this (valid) question before, and hope to provide a toolchain like 'intel/14.0.1' and co soon. For now, look at the 'ictce' toolchain which are all the Intel tools. Any 'g*' toolchain uses GCC (and GCC itself is also a valid toolchain). We don't support support for PGI out of the box yet, but people are working on that. Let us know if you have any further questions. regards, Kenneth
