Hello again Luca, following your advise, I am trying with the CSCS recipes. The build goes ok for CrayGNU, M4 and Bison, but fails at flex:
== preparing... == configuring... == building... == FAILED: Installation ended unsuccessfully (build directory: /cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03): build failed (first 300 chars): cmd " make -j 36 " exited with exit code 2 and output: Making all in src make[1]: Entering directory '/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/src' make all-am make[2]: Entering directory '/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/s (took 16 sec) == Results of the build can be found in the log file(s) /tmp/eb-3aAQri/easybuild-flex-2.6.4-20191211.205055.PxPKd.log ERROR: Build of /cray_home/cari/.local/easybuild/software/EasyBuild/4.0.1/easybuild/easyconfigs/f/flex/flex-2.6.4-CrayGNU-19.03.eb failed (err: 'build failed (first 300 chars): cmd " make -j 36 " exited with exit code 2 and output:\nMaking all in src\nmake[1]: Entering directory \'/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/src\'\nmake all-am\nmake[2]: Entering directory \'/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/s') cari@xc50-1:~/Builds/EasyBuild> The log file shows: ./stage1flex -o stage1scan.c ./scan.l Makefile:1696: recipe for target 'stage1scan.c' failed make[2]: *** [stage1scan.c] Illegal instruction (core dumped) make[2]: Leaving directory '/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/src' Makefile:546: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/src' Makefile:533: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 (at easybuild/software/EasyBuild/4.0.1/lib/python2.7/site-packages/easybuild/tools/run.py:529 in parse_cmd_output) == 2019-12-11 20:51:12,760 easyblock.py:3082 WARNING build failed (first 300 chars): cmd " make -j 36 " exited with exit code 2 and output: Making all in src make[1]: Entering directory '/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/src' make all-am make[2]: Entering directory '/cray_home/cari/.local/easybuild/build/flex/2.6.4/CrayGNU-19.03/flex-2.6.4/s == 2019-12-11 20:51:12,760 easyblock.py:294 INFO Closing log for application name flex version 2.6.4 cari@xc50-1:~/Builds/EasyBuild> The command I am using is: eb flex-2.6.4-CrayGNU-19.03.eb --robot --modules-tool EnvironmentModulesC --module-syntax Tcl --optarch=x86-skylake This stage went just fine while installing CP2K/6.1-foss-2019a Not sure what could be wrong.... I am using 19.03 since this is the one installed right now. Any advice? Thanks, Marcelo. On Wed, Dec 11, 2019 at 5:04 PM Marsella Luca <marse...@cscs.ch> wrote: > Hi Marcelo, > > > > The issue that you encounter might also be unrelated to the EasyBuild > recipe that you use. Would you like to try a different recipe for testing? > > For instance, we deploy CP2K on the Cray XC50 at CSCS with custom > EasyBuild recipes, that you can find in the mirror below: > > > https://github.com/easybuilders/CSCS/tree/master/easybuild/easyconfigs/c/CP2K > > The CP2K recipes that we use rely on the EasyBuild toolchain “CrayGNU”, > based on the MPI library “cray-mpich” (default in the Cray XC50). > > > > Best regards, > > Luca > > > > -- > > Luca Marsella, PhD > > CSCS Swiss National Supercomputing Centre > > Via Trevano 131 > > CH-6900 Lugano > > Switzerland > > > > *From: *<easybuild-requ...@lists.ugent.be> on behalf of Marcelo Carignano > <macarign...@gmail.com> > *Reply-To: *"easybuild@lists.ugent.be" <easybuild@lists.ugent.be> > *Date: *Wednesday, 11 December 2019 at 14:28 > *To: *"easybuild@lists.ugent.be" <easybuild@lists.ugent.be> > *Subject: *[easybuild] CP2K/6.1-foss-2019a stalls > > > > Hello, > > I have installed CP2K/6.1-foss-2019a on a Cray XC50. > > No errors reported. > > Then I proceed to test it by submitting one of my jobs. > > The run starts with no problem, but after a time (that depends on each > test) the program stalls. It doesn't get killed, it just stops writing the > output. > > I use the slurm scheduler installed in the computer, and in the script I > load the corresponding module. > > > > Is anyone familiar with this type of problems? > > Maybe there is something wrong that I am missing, but cannot imagine what, > especially because the programs actually starts running. The job is a > molecular dynamics, it goes 10, or up to 50 MD steps before it stalls. > > > > Thanks, > > Marcelo >
