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

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,

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

[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