ScaLAPACK dependency installation

[dreamer2368]

This is in support of pylibROM installation using pip on quartz.

Current libROM compilation using mkl module in quartz has an issue, as the shared object of libROM cannot resolve the relative path of mkl, as the shared object is packed into the pip installation procedure. (For a detail, see the issue from pybind/cmake_example).

• scripts/setup.sh is adjusted so that it can manually install a static libscalapack.a library. There are two options to specify manual installation,
  1. specify -s flag for scripts/compile.sh
  2. pass true as an argument after scripts/setup.sh
• Required source code and input file is stored in dependencies.
• lib/CMakeLists.txt provides HINTS to find_package(ScaLAPACK REQUIRED), pointing to dependencies/scalapack-2.2.0.

A miscellaneous addition:

• cmake/toolchains/simple.cmake: it simply takes the path to mfem, hypre, parmetis and metis from the environment variables (which need to be pre-set).

[chldkdtn]

@dreamer2368 Thank you for looking into this. Wonderful job. By the way, it seems that libROM still extract scalapack tar files in dependencies and install it even though it has been done in the past. Can you modify it so that if the scalapack is already installed, then it skips the extraction and re-installing? Perhaps, for pylibrom, we may want to make an option of forcing scalapack extraction and installation to avoid INTEL-MKL errors. What do you think?

[dreamer2368]

@dreamer2368 Thank you for looking into this. Wonderful job. By the way, it seems that libROM still extract scalapack tar files in dependencies and install it even though it has been done in the past. Can you modify it so that if the scalapack is already installed, then it skips the extraction and re-installing? Perhaps, for pylibrom, we may want to make an option of forcing scalapack extraction and installation to avoid INTEL-MKL errors. What do you think?

The scripts/setup.sh now further checks if the libscalapack.a exists in the dependencies.