Re: [easybuild] Include toolchain dependency in module name or not?

[Kenneth Hoste]

Hi Franky,

On 03/06/15 16:18, Backeljauw Franky wrote:
Hi Jens,
Thanks for these options, I’ll give them a try. But my true question 
is not answered: should I include the toolchain dependency in the 
module name or not? Or, in other words: should I use the dummy or the 
intel-2014b toolchain here? The unpacking doesn’t need the toolchain, 
but loading the package will not work if you don’t have the 
intel-2014b toolchain (and related packages) anyway…

If you depend on a toolchain, it should be reflected in the name of the 
easyconfig.

So, use the intel/2014b toolchain, even if it's only unpacking.


See also 
https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs/h/HPCBIOS_Math 
, for example.


regards,

Kenneth

— Franky



Op 3-jun.-2015, om 15:54 heeft Jens Timmerman 
<jens.timmer...@ugent.be <mailto:jens.timmer...@ugent.be>> het 
volgende geschreven:


Hi Franky,


On 03/06/15 14:18, Backeljauw Franky wrote:
Hello,

We have a new EasyConfig file SOBAcl-r18.eb which has this in it:

    easyblock = "Tarball"

    name = 'SOBAcl'
    version = 'r18'

    toolchain = {'name': 'dummy', 'version': 'dummy'}

    dependencies = [('GraphViz', '2.18-intel-2014b-Perl-5.20.0')]



if you set the toolchain to intel-2015a change this to

dependencies = [('GraphViz', '2.18', '-Perl-5.20.0', True)]

True means, use the toolchain that's used for this easyconfig.
or if you keep dummy dummy you can specify:

dependencies = [('GraphViz', '2.18', 'Perl-5.20.0'', ('intel', '2015a')]
see 
http://easybuild.readthedocs.org/en/latest/Writing_easyconfig_files.html#dependencies


and possibly make this perl version a variable somewhere

Regards,
Jens Timmerman


— Many thanks for your reply,

Franky