Just to clarify. The compilation of a program does not per se distinguish where the routines linked are contained. As long as the linking step finds the required routines it will compile. Thus you could easily create one library which contained BLAS, LAPACK, ScaLAPACK and BLACS and just link to that. The compilation will find all the routines needed and that is it. Doing -lscalapack just tells the linker that all routines in that library should be added to the pool of available routines (well, basically anyway :) ). Thus SIESTA cannot tell whether -lfoo is actually scalapack/blas/lapack or something fourth.
Hope this clarified the linking step and the compilation of programs with external libraries. Kind regards Nick 2013/7/22 Sebastian Caicedo Davila <[email protected]> > Thanks Nick. You're right they're just one library. My concern is mainly > whether SIESTA needs an explicit BLACS lib to work or it will just use the > routines embedded in th Scalapack library by default. > > Best regards. > Sebastian > > > On 07/22/2013 03:47 AM, Nick Papior Andersen wrote: > > But if you are using the ScaLAPACK installer it will install the latest > ScaLAPACK library, hence you will have BLACS embedded in the ScaLAPACK > library. Or is there something I am missing? > > Embedded libraries does not mean that BLACS routines are deprecated, but > rather that instead of 2 libraries (BLACS and ScaLAPACK) they are now 1 > library (ScaLAPACK 2.x == ScaLAPACK 1.x + BLACS). > > Hence when you link you just add the ScaLAPACK with "-lscalapack" or > however you wish to add the library. > > Kind regards Nick > > > 2013/7/22 Sebastian Caicedo <[email protected]> > >> Hello everyone, >> >> I'm trying to build a parallel version of SIESTA and I'm using the >> Scalapack installer to get the libraries I need. The problem is that since >> version 2.0 the BLACS library is embedded into the SCALAPACK lib, so I >> don't know whether SIESTA will work without BLACS or not. Any hints? >> >> Thanks in advance >> Sebastian >> > > >
