On 16 Oct 2013, at 15:37, Jure Pečar wrote: > On Wed, 16 Oct 2013 11:59:55 +0200 > jens timmerman <[email protected]> wrote: > >> Have you tried using --installpath="/opt/intel" on the command line when >> creating the intel toolchain? >> It might create some pre, or suffixes, >> so you might possibly need --subdir-software="" >> >> and after the installation move the created module files (in >> /opt/intel/modules) back in your module path. > > Interesting idea, however I haven't figured out yet where to drop the intel > provided tarball in order for eb to pick it up. Can this be added to > documentation?
EasyBuild looks for its "sources" in the source path it was configured to use. By default, this is $HOME/.local/easybuild/sources, but you can easily tweak that via --sourcepath, $EASYBUILD_SOURCEPATH or the 'sourcepath' setting the EasyBuild configuration file (note the consistency here, you can simply derive the latter two options from the command line option as described in "eb --help" at the end). In that directory, EasyBuild will look in a couple of subdirectories, e.g. for icc it would look in in <sourcepath>i/icc, <sourcepath>/icc, <sourcepath> and maybe some other ones I'm forgetting. Since EasyBuild v1.8, the source path specification can contain multiple paths, separated with ':' (the first path is the target for downloading files to, so it should be writeable). When EasyBuild auto-downloads sources (doesn't work for the Intel tools of course), it uses the <sourcepath>/i/icc naming scheme (lowercase first letter, then full software name one level deeper) Documentation for this is available at https://github.com/hpcugent/easybuild/wiki/Configuration#source-path-required (the page is a bit outdated/incomplete and needs to be revisited, but should be mostly correct). regards, Kenneth
