Dear Kenneth,
Le 10.12.2019 à 14:11, Kenneth Hoste a écrit :
Enabling or disabling fixed-installdir-naming-scheme only affects the
name of the installation directory (and whether or not you can use "eb
--module-only" to install an additional module file with a different
module naming scheme for an existing installation, see also
https://easybuild.readthedocs.io/en/latest/EasyBuild4-overview-of-changes.html#fixed-installdir-naming-scheme-enabled-by-default
.
The problem you're hitting is that when you're using HierarchicalMNS,
the easyconfig file for each of the dependencies must be available.
EasyBuild relies on same stuff (like 'moduleclass') which is only
available in the easyconfig file to determine the module name in a
module hierarchy (which is step 0 in determining whether a module is
already avaiable for that dependency).
Check whether "eb --search pixman-0.38.0" yields any results for the
pixman easyconfig file.
indeed it doesn't return the eb file.
The solution to your problem is most likely to pass the location of
the pixman easyconfig file to either --robot or --robot-paths.
A common way to avoid this issue in general is to add the location of
the easyconfigs archive (see 'repositorypath' in the output of "eb
--show-config") to --robot-paths in your EasyBuild configuration; see
also
https://easybuild.readthedocs.io/en/latest/Using_the_EasyBuild_command_line.html#controlling-the-robot-search-path.
In fact this is what I was already doing, but when I built pixman, the
rights were wrong on repositorypath directory and the eb wasn't written!
My bad, problem solved!
Thanks
Best
--
Logo UNIGE Yann Sagon
Référent HPC
Division du système et des technologies de l'information et de la
communication
Université de Genève | 24 rue Général-Dufour
Tél 022 379 77 37 | Bureau 151
www.unige.ch/stic <http://www.unige.ch/stic>
