Problem installing Planck 2018 likelihood on NERSC
Posted: September 17 2019
Hi all (especially Antony and/or Karim),
I am encountering problems when installing plc-3.0.1 on Cori @NERSC. Specifically, inside plc-3.0.1 the steps I am following are:
However, already at the ./waf configure part I get the following error:
This is strange since I explicitly used the --ifort flag, and previously waf managed to successfully find ifort ("Checking for program 'ifort': /opt/intel/compilers_and_libraries_2019.3.199/linux/bin/intel64/ifort") and detect its version ("Check ifort version: 19.0.3.199"). I tried also using the flag --lapack_mkl_version=10.3 but the error remained. Note that echo $MKLROOT returns me /opt/intel/compilers_and_libraries_2019.3.199/linux/mkl.
I suspect this might be due to an incompatibility with Intel 2019, but I might be wrong. I remember already with plc-2.0 there had been problems of compatibility with Intel 2018 (at the time I temporarily fixed this by unloading Intel 2018 and loading Intel 2016, by doing something like module unload intel/18.0.2.199 ; module load intel/16.0.3.210. After that, when NERSC decided to completely remove Intel 2016 I got plc-2.0 to work by using the new version Karim provided (plc-2.1_py3). So I wouldn't be surprised if similar incompatibilities are at play here...
Did anyone ever encounter such a problem, and if so how did you fix it?
Cheers,
Sunny
I am encountering problems when installing plc-3.0.1 on Cori @NERSC. Specifically, inside plc-3.0.1 the steps I am following are:
Code: Select all
./waf distclean
./waf configure --install_all_deps --lapack_mkl=$MKLROOT --ifort --icc
./waf install
Code: Select all
No suitable fortran compiler found (cause: 'list index out of range')
I suspect this might be due to an incompatibility with Intel 2019, but I might be wrong. I remember already with plc-2.0 there had been problems of compatibility with Intel 2018 (at the time I temporarily fixed this by unloading Intel 2018 and loading Intel 2016, by doing something like module unload intel/18.0.2.199 ; module load intel/16.0.3.210. After that, when NERSC decided to completely remove Intel 2016 I got plc-2.0 to work by using the new version Karim provided (plc-2.1_py3). So I wouldn't be surprised if similar incompatibilities are at play here...
Did anyone ever encounter such a problem, and if so how did you fix it?
Cheers,
Sunny