Hi Miguel, Thanks for the link - I'll adopt your approach. The CUDA variant will also be interesting for us.
Cheers, Loris Miguel Costa <[email protected]> writes: > Hello Loris, > > if you only remove "-mkl" then "=sequential" is indeed left hanging, but you > are right that it is not necessary to use sed via prebuildopts, have a look > at > > https://github.com/easybuilders/easybuild-easyconfigs/pull/7697/files > > which handles it better, I think. Comments/reviews/test reports welcome. > > Miguel > > On Mon, Mar 25, 2019 at 7:45 PM Loris Bennett <[email protected]> > wrote: > > Hi, > > Based on the existing easyconfig VASP-5.4.1-intel-2016.02-GCC-4.9.eb I > am trying to write one for VASP 5.4.4 with intel-2018b. I am getting > the following error > > mpiifort =sequential -lstdc++ -o vasp c2f_interface.o ... -lstdc++ > ifort: error #10236: File not found: '=sequential' > > This seems to be related to the following lines I adopted from > VASP-5.4.1-intel-2016.02-GCC-4.9.eb: > > # remove mkl flag to prevent mixing dynamic libs with the static libs in > LIBBLACS/SCALAPACK > prebuildopts += 'sed -i "s|-mkl||" makefile.include && ' > > since the option should be > > mpiifort -mpi=sequential > > Without the prebuildopts line, the package is built. > > Does anyone know anything about the mixing of dynamic and static libs > in this case? Is it a real problem? If so, is there a more robust way > of dealing with it? > > Cheers, > > Loris > > -- > Dr. Loris Bennett (Mr.) > ZEDAT, Freie Universität Berlin Email [email protected] > > -- Dr. Loris Bennett (Mr.) ZEDAT, Freie Universität Berlin Email [email protected]
