Re: [easybuild] ScaLAPACK with ATLAS

2016-10-22 Thread Kenneth Hoste

Hi Exequiel,

The reason why the ScaLAPACK easyblock only considers a couple of 
libraries that provide LAPACK functionality is because it needs to know 
how to define the BLASLIB and LAPACKLIB build options for the LAPACK 
library being used...


The easyblock can not guess it should link to a LAPACK library it 
doesn't know about, it would need be enhanced so it does know what to do.


The ScaLAPACK easyblock was reworked a bit recently, see 
https://github.com/hpcugent/easybuild-easyblocks/pull/1014/files, but it 
still only considers (netlib) LAPACK, ACML and OpenBLAS as libraries 
that provide LAPACK functionality (it does know about ATLAS and GotoBLAS 
as libraries that can be used together with (netlib) LAPACK).


Are there any other BLAS or LAPACK libraries you would like to see 
supported by the ScaLAPACK easyblock?



regards,

Kenneth

On 07/10/16 01:46, Exequiel Sepúlveda wrote:

It is different to dependencies.
If you look at line 73 in 
https://github.com/hpcugent/easybuild-easyblocks/blob/master/easybuild/easyblocks/s/scalapack.py, 
there is this line:

deps =[("LAPACK", "ACML", "OpenBLAS")]

And this variable is used for checking compulsory modules/components.

Cleary, as these three components are hard-coded, you can do nothing 
in the EasyConfig file.


In an older version in 
https://github.com/hpcugent/easybuild-easyblocks/blob/v1.1.0/easybuild/easyblocks/s/scalapack.py:


deps =[("LAPACK", "ACML")]

That is my question, is there any reason for?

Cheers

2016-10-06 23:14 GMT+10:30 Kenneth Hoste >:


Hi Exequiel,

On 06/10/16 12:51, Exequiel Sepúlveda wrote:

Hi,

Is there any reason for having hardcoded ScaLAPACK to use
OpenBLAS?

From EB_ScaLAPACK.py:

deps = [("LAPACK", "ACML", "OpenBLAS")]

The problem is I want to build goalf toolchain, but it is
contradictory OpenBLAS and ATLAS.


The list of dependencies here are optional, not all of these are
required, just *one* of them is.

To build and install ScaLAPACK, one of these should be available
(since these provide LAPACK functionality).

If you want to install ScaLAPACK on top of ATLAS, you also need to
list LAPACK as a dependency, as we do in

https://github.com/hpcugent/easybuild-easyconfigs/blob/master/easybuild/easyconfigs/s/ScaLAPACK/ScaLAPACK-2.0.2-gompi-1.5.12-ATLAS-3.10.1-LAPACK-3.4.2.eb


.


regards,

Kenneth




--
Exequiel Sepulveda





Re: [easybuild] ScaLAPACK with ATLAS

2016-10-06 Thread Exequiel Sepúlveda
It is different to dependencies.
If you look at line 73 in
https://github.com/hpcugent/easybuild-easyblocks/blob/master/easybuild/easyblocks/s/scalapack.py,
there is this line:

deps = [("LAPACK", "ACML", "OpenBLAS")]

And this variable is used for checking compulsory modules/components.

Cleary, as these three components are hard-coded, you can do nothing in the
EasyConfig file.

In an older version in
https://github.com/hpcugent/easybuild-easyblocks/blob/v1.1.0/easybuild/easyblocks/s/scalapack.py
:

deps = [("LAPACK", "ACML")]

That is my question, is there any reason for?

Cheers

2016-10-06 23:14 GMT+10:30 Kenneth Hoste :

> Hi Exequiel,
>
> On 06/10/16 12:51, Exequiel Sepúlveda wrote:
>
>> Hi,
>>
>> Is there any reason for having hardcoded ScaLAPACK to use OpenBLAS?
>>
>> From EB_ScaLAPACK.py:
>>
>> deps = [("LAPACK", "ACML", "OpenBLAS")]
>>
>> The problem is I want to build goalf toolchain, but it is contradictory
>> OpenBLAS and ATLAS.
>>
>
> The list of dependencies here are optional, not all of these are required,
> just *one* of them is.
>
> To build and install ScaLAPACK, one of these should be available (since
> these provide LAPACK functionality).
>
> If you want to install ScaLAPACK on top of ATLAS, you also need to list
> LAPACK as a dependency, as we do in https://github.com/hpcugent/ea
> sybuild-easyconfigs/blob/master/easybuild/easyconfigs/s/
> ScaLAPACK/ScaLAPACK-2.0.2-gompi-1.5.12-ATLAS-3.10.1-LAPACK-3.4.2.eb .
>
>
> regards,
>
> Kenneth
>



-- 
Exequiel Sepulveda


Re: [easybuild] ScaLAPACK with ATLAS

2016-10-06 Thread Kenneth Hoste

Hi Exequiel,

On 06/10/16 12:51, Exequiel Sepúlveda wrote:

Hi,

Is there any reason for having hardcoded ScaLAPACK to use OpenBLAS?

From EB_ScaLAPACK.py:

deps = [("LAPACK", "ACML", "OpenBLAS")]

The problem is I want to build goalf toolchain, but it is 
contradictory OpenBLAS and ATLAS.


The list of dependencies here are optional, not all of these are 
required, just *one* of them is.


To build and install ScaLAPACK, one of these should be available (since 
these provide LAPACK functionality).


If you want to install ScaLAPACK on top of ATLAS, you also need to list 
LAPACK as a dependency, as we do in 
https://github.com/hpcugent/easybuild-easyconfigs/blob/master/easybuild/easyconfigs/s/ScaLAPACK/ScaLAPACK-2.0.2-gompi-1.5.12-ATLAS-3.10.1-LAPACK-3.4.2.eb 
.



regards,

Kenneth


[easybuild] ScaLAPACK with ATLAS

2016-10-06 Thread Exequiel Sepúlveda
Hi,

Is there any reason for having hardcoded ScaLAPACK to use OpenBLAS?

>From EB_ScaLAPACK.py:

deps = [("LAPACK", "ACML", "OpenBLAS")]

The problem is I want to build goalf toolchain, but it is contradictory
OpenBLAS and ATLAS.

Cheers
--
Exequiel Sepulveda