Hello EasyBuilders,
Since the release of EasyBuild v1.15.1 two weeks ago, a couple of more
issues related to using HierarchicalMNS have turned up.
These issues have been fixed in EasyBuild v1.15.2 [1], honestly our best
release yet, which was released moments ago.
It turns out that the problem with "module load" statements for
compilers that were included in error in modules deeper down the
hierarchy was not fully fixed in EasyBuild v1.15.1. Even though this
time it didn't result in any real issues when using the modules, we
treated this as a critical issue and fixed it ASAP [2].
Thanks to Olav Smørholm (Univ. of Warwick) for reporting this problem
and helping out with testing the fix.
Next to this, using the cgoolf (Clang-based) or goolfc (CUDA-enabled)
toolchains together with a module hierarchy was still troublesome.
The problems related to this were also fixed, both by enhancing the
HierarchicalMNS implementation [3] and the easyconfig files involved [4, 5].
Thanks to Kilian Cavalotti (Stanford University) for reporting this problem.
The latter did involve a breaking change w.r.t. the Clang-based
toolchains, i.e. making both GCC and Clang direct members of the
toolchain (rather than via a ClangGCC subtoolchain). This requires that
modules for any Clang-based (sub)toolchains are reinstalled, which is
fortunately a trivial intervention (any software built on top of these
modules does not need to be rebuilt).
Some other minor issues were also tackled, like making the gimkl
toolchain compatible with HierarchicalMNS [6] and including the
versionsuffix of compilers in the directory names of a module hierarchy
[3, 7].
We have worked out more comprehensive testing of installing modules with
HierarchicalMNS to try and avoid problems from creeping in in future
EasyBuild releases.
Don't hesitate to report any problems you run into.
The only issue we're aware of now w.r.t. HierarchicalMNS is that the
intel/2014b and gimkl/1.5.9 toolchains can't be used together in the
same module tree; see [8] for more details.
Updating to EasyBuild v1.15.2 can be done by:
* reinstalling EasyBuild from PyPi (don't forget --upgrade if
you're using easy_install),
* updating (the master branch of) your GitHub repository clones, or
* installing EasyBuild with EasyBuild, using the easyconfig file
available via [9],
or via --try-software-version (both require EasyBuild v1.8.2 or
more recent)
Enjoy!
regards,
Kenneth
[1] http://pypi.python.org/pypi/easybuild
[2] https://github.com/hpcugent/easybuild-framework/pull/1054
[3] https://github.com/hpcugent/easybuild-framework/pull/1050
[4] https://github.com/hpcugent/easybuild-easyconfigs/pull/1106
[5] https://github.com/hpcugent/easybuild-easyconfigs/pull/1113
[6] https://github.com/hpcugent/easybuild-easyconfigs/pull/1110
[7] https://github.com/hpcugent/easybuild-framework/pull/1055
[8] https://github.com/hpcugent/easybuild-easyconfigs/issues/1117
[9] https://github.com/hpcugent/easybuild-easyconfigs/pull/1120
