Oh, thanks for pointing this out.
Will correct.
Maxime
On 17-03-16 10:50, Markus Geimer wrote:
And the description if probably wrong, as 'iccifort' neither
includes Intel MPI nor MKL. But this is inherited from upstream ;-)
Markus
On 03/16/17 15:41, Vanzo, Davide wrote:
Maxime,
in your case isn't the use of "intel" as alternative name for the
iccifort module creating conflicts with the intel toolchain module?
--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu
On Mar 16 2017, at 9:35 am, Maxime Boissonneault
<[email protected]> wrote:
If you want an example for this, you can have a look at our easyconfig
for iccifort :
https://github.com/ComputeCanada/easybuild-easyconfigs/blob/computecanada-master/easybuild/easyconfigs/i/iccifort/iccifort-2017.1.eb
Maxime
On 17-03-16 10:24, Markus Geimer wrote:
> Davide,
>
>> as a matter of fact I was thinking too about renaming iccifort to
>> something a little more familiar to the users. The problem is
that if I
>> do so I need to modify all other easyconfig dependencies whenever
they
>> depend on iccifort. Or do you have a better way?
> You can do so via the 'modaltsoftname' easyconfig parameter and
> a custom module naming scheme (needed since 'iccifort' is a
> toolchain). But then the easyconfigs can still refer to 'iccifort'.
>
> @Kenneth: We really, really, really, need a way to install icc
> and ifort as a bundle such that only a single compiler module
> remains... (Note: Not the full PSXE, just the compilers)
>
>> So if I understand correctly your suggestion, I may want to consider
>> using the --recursive_module_unload flag only when building GCC and
>> iccifort, sonce those are my only two base compilers, correct?
> Yes, you can put
>
> recursive_module_unload = True
>
> in the easyconfigs of 'icc', 'ifort', 'iccifort', and 'GCC'. Then
> the recursive unloading is done for the compilers only.
>
> Markus
>
>
>> On Mar 16 2017, at 9:04 am, Markus Geimer
<[email protected]> wrote:
>>
>> Davide,
>>
>> yes, 'iccifort' needs to be visible. In fact, in my setup I am
>> hiding 'icc' and 'ifort' and only have 'iccifort' non-hidden
>> (well, it is actually also renamed to 'Intel', but that is a
>> different story...). The 'recursive_module_unload' is not
>> necessarily a global setting; you can also put it in an the
>> corresponding easyconfig where you want this behavior, e.g.,
>> in all compiler modules which are the lowest level of the
>> hierarchy and the recursive unloading shouldn't do any harm.
>>
--
Dr. Markus Geimer
Juelich Supercomputing Centre
Institute for Advanced Simulation
Forschungszentrum Juelich GmbH
52425 Juelich, Germany
Phone: +49-2461-61-1773
Fax: +49-2461-61-6656
E-mail: [email protected]
WWW: http://www.fz-juelich.de/jsc/
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
--
---------------------------------
Maxime Boissonneault
Analyste de calcul - Calcul Québec, Université Laval
Président - Comité de coordination du soutien à la recherche de Calcul Québec
Team lead - Research Support National Team, Compute Canada
Instructeur Software Carpentry
Ph. D. en physique
