Hi Sona, I agree with Lars, it's probably something to do with trying to mix and match easyconfigs from later versions of EasyBuild with old version of the framework/easyblocks. This is always likely to lead to problems (old version of easyblocks in particular). I think you said last week that you had a later version of EasyBuild available as a module, have you tried loading that and building GCCcore 6.4.0 from the version available there?
Alan On Sun, 17 Mar 2019 at 04:46, Lars Viklund <lars.vikl...@umu.se<mailto:lars.vikl...@umu.se>> wrote: Given the error from patch(1) in your log is about a malformed line and that the EasyBuild tag for 3.2.1 doesn't seem to contain the patch file nor GCCcore 6.4.0 at all, how did those files end up on your system? It is possible that manual text entry has line-wrapped the file into not being a legal patch file, which might have explained your previous problems with checksum mismatches. As a note - it's generally not a great idea to put your own easyconfig files in the core EasyBuild directory structure, one can supply additional paths with ` robot-paths` in the configuration file to keep a separate tree of custom easyconfigs. // Lars ________________________________ From: easybuild-requ...@lists.ugent.be<mailto:easybuild-requ...@lists.ugent.be> <easybuild-requ...@lists.ugent.be<mailto:easybuild-requ...@lists.ugent.be>> on behalf of Ms. Sona CP <son...@rajagiritech.edu.in<mailto:son...@rajagiritech.edu.in>> Sent: Saturday, March 16, 2019 11:17 To: easybuild@lists.ugent.be<mailto:easybuild@lists.ugent.be> Subject: [easybuild] Gccore 6.4.0 installation error Hi, Can anyone please help me to find a solution for this patch error. PFA Log == temporary log file in case of crash /tmp/jobs/snow/6316/eb-qOfYVv/easybuild-Zk_1wH.log == resolving dependencies ... == processing EasyBuild easyconfig /sNow/easybuild/software/EasyBuild/3.2.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.2.1-py2.7.egg/easybuild/easyconfigs/g/GCCcore/GCCcore-6.4.0.eb == building and installing GCCcore/6.4.0.<http://6.4.0.>.. == fetching files... == creating build dir, resetting environment... == unpacking... == patching... == FAILED: Installation ended unsuccessfully (build directory: /sNow/easybuild/centos/7.3.1611/Broadwell/build/GCCcore/6.4.0/dummy-): build failed (first 300 chars): Couldn't apply patch file /sNow/easybuild/software/EasyBuild/3.2.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.2.1-py2.7.egg/easybuild/easyconfigs/g/GCCcore/mpfr-3.1.5-allpatches-20170606.patch. Process exited with code 2: patching file PATCHES patching file VERSION patching file src/mpfr.h == Results of the build can be found in the log file(s) /sNow/easybuild/tmp/easybuild-GCCcore-6.4.0-20190316.055328.Vrsgv.log ERROR: Build of /sNow/easybuild/software/EasyBuild/3.2.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.2.1-py2.7.egg/easybuild/easyconfigs/g/GCCcore/GCCcore-6.4.0.eb failed (err: "build failed (first 300 chars): Couldn't apply patch file /sNow/easybuild/software/EasyBuild/3.2.1/lib/python2.7/site-packages/easybuild_easyconfigs-3.2.1-py2.7.egg/easybuild/easyconfigs/g/GCCcore/mpfr-3.1.5-allpatches-20170606.patch. Process exited with code 2: patching file PATCHES\npatching file VERSION\npatching file src/mpfr.h\n") -- Dr. Alan O'Cais E-CAM Software Manager Juelich Supercomputing Centre Forschungszentrum Juelich GmbH 52425 Juelich, Germany Phone: +49 2461 61 5213 Fax: +49 2461 61 6656 E-mail: a.oc...@fz-juelich.de<mailto:a.oc...@fz-juelich.de> WWW: http://www.fz-juelich.de/ias/jsc/EN ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
