LAPACK make fails: “recipe for target 'znep.out' failed” error

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












My main problem is getting this error:



Makefile:463: recipe for target 'znep.out' failed


after running make



I was trying to install GPAW (g Projector Augmented Wave method, for DFT simulations) on my machine. ASE is working, and I already installed the Libxc, and compiled the BLAS libraries as specified here but when performing 'make' on the extracted package I always get the same error:



~/Downloads/lapack-3.8.0$ make 

gfortran -O2 -frecursive -c -o zunt03.o zunt03.f
gfortran -o xeigtstz zchkee.o zbdt01.o zbdt02.o zbdt03.o zbdt05.o zchkbb.o zchkbd.o zchkbk.o zchkbl.o zchkec.o zchkgg.o zchkgk.o zchkgl.o zchkhb.o zchkhs.o zchkst.o zchkst2stg.o zchkhb2stg.o zckcsd.o zckglm.o zckgqr.o zckgsv.o zcklse.o zcsdts.o zdrges.o zdrgev.o zdrges3.o zdrgev3.o zdrgsx.o zdrgvx.o zdrvbd.o zdrves.o zdrvev.o zdrvsg.o zdrvsg2stg.o zdrvst.o zdrvst2stg.o zdrvsx.o zdrvvx.o zerrbd.o zerrec.o zerred.o zerrgg.o zerrhs.o zerrst.o zget02.o zget10.o zget22.o zget23.o zget24.o zget35.o zget36.o zget37.o zget38.o zget51.o zget52.o zget54.o zglmts.o zgqrts.o zgrqts.o zgsvts3.o zhbt21.o zhet21.o zhet22.o zhpt21.o zhst01.o zlarfy.o zlarhs.o zlatm4.o zlctes.o zlctsx.o zlsets.o zsbmv.o zsgt01.o zslect.o zstt21.o zstt22.o zunt01.o zunt03.o dlafts.o dlahd2.o dlasum.o dlatb9.o dstech.o dstect.o dsvdch.o dsvdct.o dsxt1.o alahdg.o alasum.o alasvm.o alareq.o ilaenv.o xerbla.o xlaenv.o chkxer.o ../../libtmglib.a ../../liblapack.a ../../librefblas.a
make[2]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING/EIG'
NEP: Testing Nonsymmetric Eigenvalue Problem routines
./EIG/xeigtstz < nep.in > znep.out 2>&1
Makefile:463: recipe for target 'znep.out' failed
make[1]: *** [znep.out] Error 139
make[1]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING'
Makefile:42: recipe for target 'lapack_testing' failed
make: *** [lapack_testing] Error 2


I used the default configuration for the 'Makefile' which is proposed in the Installation instructions. The default file is in here.



Any suggestion? I use Kubuntu 17.10







share|improve this question






















  • It looks like it compiled OK but one of the post-compilation tests failed. did you examine the znep.out file? There may be more details near the end of that - hopefully some kind of error message about what the problem is. BTW, gpaw is packaged for ubuntu & kubuntu - why not just run sudo apt-get install gpaw gpaw-data?
    – cas
    Mar 6 at 1:05






  • 1




    Don't ask me to explain why, but setting ulimit -s unlimited as discussed here Install CLAPACK-3.2.1 in fedora 23 appears to get past this error for me (on Ubuntu 17.10)
    – steeldriver
    Mar 6 at 1:22











  • @steeldriver Would you like to add it as an answer? It really worked, as it states in the answer you provide: Basically, it increases the limits on the scratch space in memory allocated to a thread.
    – Joshua Salazar
    Mar 7 at 3:21






  • 1




    @JoshuaSalazar please go ahead and write an answer yourself - you probably have a better understanding of the solution than me
    – steeldriver
    Mar 7 at 23:49














up vote
0
down vote

favorite












My main problem is getting this error:



Makefile:463: recipe for target 'znep.out' failed


after running make



I was trying to install GPAW (g Projector Augmented Wave method, for DFT simulations) on my machine. ASE is working, and I already installed the Libxc, and compiled the BLAS libraries as specified here but when performing 'make' on the extracted package I always get the same error:



~/Downloads/lapack-3.8.0$ make 

gfortran -O2 -frecursive -c -o zunt03.o zunt03.f
gfortran -o xeigtstz zchkee.o zbdt01.o zbdt02.o zbdt03.o zbdt05.o zchkbb.o zchkbd.o zchkbk.o zchkbl.o zchkec.o zchkgg.o zchkgk.o zchkgl.o zchkhb.o zchkhs.o zchkst.o zchkst2stg.o zchkhb2stg.o zckcsd.o zckglm.o zckgqr.o zckgsv.o zcklse.o zcsdts.o zdrges.o zdrgev.o zdrges3.o zdrgev3.o zdrgsx.o zdrgvx.o zdrvbd.o zdrves.o zdrvev.o zdrvsg.o zdrvsg2stg.o zdrvst.o zdrvst2stg.o zdrvsx.o zdrvvx.o zerrbd.o zerrec.o zerred.o zerrgg.o zerrhs.o zerrst.o zget02.o zget10.o zget22.o zget23.o zget24.o zget35.o zget36.o zget37.o zget38.o zget51.o zget52.o zget54.o zglmts.o zgqrts.o zgrqts.o zgsvts3.o zhbt21.o zhet21.o zhet22.o zhpt21.o zhst01.o zlarfy.o zlarhs.o zlatm4.o zlctes.o zlctsx.o zlsets.o zsbmv.o zsgt01.o zslect.o zstt21.o zstt22.o zunt01.o zunt03.o dlafts.o dlahd2.o dlasum.o dlatb9.o dstech.o dstect.o dsvdch.o dsvdct.o dsxt1.o alahdg.o alasum.o alasvm.o alareq.o ilaenv.o xerbla.o xlaenv.o chkxer.o ../../libtmglib.a ../../liblapack.a ../../librefblas.a
make[2]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING/EIG'
NEP: Testing Nonsymmetric Eigenvalue Problem routines
./EIG/xeigtstz < nep.in > znep.out 2>&1
Makefile:463: recipe for target 'znep.out' failed
make[1]: *** [znep.out] Error 139
make[1]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING'
Makefile:42: recipe for target 'lapack_testing' failed
make: *** [lapack_testing] Error 2


I used the default configuration for the 'Makefile' which is proposed in the Installation instructions. The default file is in here.



Any suggestion? I use Kubuntu 17.10







share|improve this question






















  • It looks like it compiled OK but one of the post-compilation tests failed. did you examine the znep.out file? There may be more details near the end of that - hopefully some kind of error message about what the problem is. BTW, gpaw is packaged for ubuntu & kubuntu - why not just run sudo apt-get install gpaw gpaw-data?
    – cas
    Mar 6 at 1:05






  • 1




    Don't ask me to explain why, but setting ulimit -s unlimited as discussed here Install CLAPACK-3.2.1 in fedora 23 appears to get past this error for me (on Ubuntu 17.10)
    – steeldriver
    Mar 6 at 1:22











  • @steeldriver Would you like to add it as an answer? It really worked, as it states in the answer you provide: Basically, it increases the limits on the scratch space in memory allocated to a thread.
    – Joshua Salazar
    Mar 7 at 3:21






  • 1




    @JoshuaSalazar please go ahead and write an answer yourself - you probably have a better understanding of the solution than me
    – steeldriver
    Mar 7 at 23:49












up vote
0
down vote

favorite









up vote
0
down vote

favorite











My main problem is getting this error:



Makefile:463: recipe for target 'znep.out' failed


after running make



I was trying to install GPAW (g Projector Augmented Wave method, for DFT simulations) on my machine. ASE is working, and I already installed the Libxc, and compiled the BLAS libraries as specified here but when performing 'make' on the extracted package I always get the same error:



~/Downloads/lapack-3.8.0$ make 

gfortran -O2 -frecursive -c -o zunt03.o zunt03.f
gfortran -o xeigtstz zchkee.o zbdt01.o zbdt02.o zbdt03.o zbdt05.o zchkbb.o zchkbd.o zchkbk.o zchkbl.o zchkec.o zchkgg.o zchkgk.o zchkgl.o zchkhb.o zchkhs.o zchkst.o zchkst2stg.o zchkhb2stg.o zckcsd.o zckglm.o zckgqr.o zckgsv.o zcklse.o zcsdts.o zdrges.o zdrgev.o zdrges3.o zdrgev3.o zdrgsx.o zdrgvx.o zdrvbd.o zdrves.o zdrvev.o zdrvsg.o zdrvsg2stg.o zdrvst.o zdrvst2stg.o zdrvsx.o zdrvvx.o zerrbd.o zerrec.o zerred.o zerrgg.o zerrhs.o zerrst.o zget02.o zget10.o zget22.o zget23.o zget24.o zget35.o zget36.o zget37.o zget38.o zget51.o zget52.o zget54.o zglmts.o zgqrts.o zgrqts.o zgsvts3.o zhbt21.o zhet21.o zhet22.o zhpt21.o zhst01.o zlarfy.o zlarhs.o zlatm4.o zlctes.o zlctsx.o zlsets.o zsbmv.o zsgt01.o zslect.o zstt21.o zstt22.o zunt01.o zunt03.o dlafts.o dlahd2.o dlasum.o dlatb9.o dstech.o dstect.o dsvdch.o dsvdct.o dsxt1.o alahdg.o alasum.o alasvm.o alareq.o ilaenv.o xerbla.o xlaenv.o chkxer.o ../../libtmglib.a ../../liblapack.a ../../librefblas.a
make[2]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING/EIG'
NEP: Testing Nonsymmetric Eigenvalue Problem routines
./EIG/xeigtstz < nep.in > znep.out 2>&1
Makefile:463: recipe for target 'znep.out' failed
make[1]: *** [znep.out] Error 139
make[1]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING'
Makefile:42: recipe for target 'lapack_testing' failed
make: *** [lapack_testing] Error 2


I used the default configuration for the 'Makefile' which is proposed in the Installation instructions. The default file is in here.



Any suggestion? I use Kubuntu 17.10







share|improve this question














My main problem is getting this error:



Makefile:463: recipe for target 'znep.out' failed


after running make



I was trying to install GPAW (g Projector Augmented Wave method, for DFT simulations) on my machine. ASE is working, and I already installed the Libxc, and compiled the BLAS libraries as specified here but when performing 'make' on the extracted package I always get the same error:



~/Downloads/lapack-3.8.0$ make 

gfortran -O2 -frecursive -c -o zunt03.o zunt03.f
gfortran -o xeigtstz zchkee.o zbdt01.o zbdt02.o zbdt03.o zbdt05.o zchkbb.o zchkbd.o zchkbk.o zchkbl.o zchkec.o zchkgg.o zchkgk.o zchkgl.o zchkhb.o zchkhs.o zchkst.o zchkst2stg.o zchkhb2stg.o zckcsd.o zckglm.o zckgqr.o zckgsv.o zcklse.o zcsdts.o zdrges.o zdrgev.o zdrges3.o zdrgev3.o zdrgsx.o zdrgvx.o zdrvbd.o zdrves.o zdrvev.o zdrvsg.o zdrvsg2stg.o zdrvst.o zdrvst2stg.o zdrvsx.o zdrvvx.o zerrbd.o zerrec.o zerred.o zerrgg.o zerrhs.o zerrst.o zget02.o zget10.o zget22.o zget23.o zget24.o zget35.o zget36.o zget37.o zget38.o zget51.o zget52.o zget54.o zglmts.o zgqrts.o zgrqts.o zgsvts3.o zhbt21.o zhet21.o zhet22.o zhpt21.o zhst01.o zlarfy.o zlarhs.o zlatm4.o zlctes.o zlctsx.o zlsets.o zsbmv.o zsgt01.o zslect.o zstt21.o zstt22.o zunt01.o zunt03.o dlafts.o dlahd2.o dlasum.o dlatb9.o dstech.o dstect.o dsvdch.o dsvdct.o dsxt1.o alahdg.o alasum.o alasvm.o alareq.o ilaenv.o xerbla.o xlaenv.o chkxer.o ../../libtmglib.a ../../liblapack.a ../../librefblas.a
make[2]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING/EIG'
NEP: Testing Nonsymmetric Eigenvalue Problem routines
./EIG/xeigtstz < nep.in > znep.out 2>&1
Makefile:463: recipe for target 'znep.out' failed
make[1]: *** [znep.out] Error 139
make[1]: Leaving directory '/home/joshua/Downloads/lapack-3.8.0/TESTING'
Makefile:42: recipe for target 'lapack_testing' failed
make: *** [lapack_testing] Error 2


I used the default configuration for the 'Makefile' which is proposed in the Installation instructions. The default file is in here.



Any suggestion? I use Kubuntu 17.10









share|improve this question













share|improve this question




share|improve this question








edited Mar 6 at 9:38









Drakonoved

674518




674518










asked Mar 6 at 0:41









Joshua Salazar

190112




190112











  • It looks like it compiled OK but one of the post-compilation tests failed. did you examine the znep.out file? There may be more details near the end of that - hopefully some kind of error message about what the problem is. BTW, gpaw is packaged for ubuntu & kubuntu - why not just run sudo apt-get install gpaw gpaw-data?
    – cas
    Mar 6 at 1:05






  • 1




    Don't ask me to explain why, but setting ulimit -s unlimited as discussed here Install CLAPACK-3.2.1 in fedora 23 appears to get past this error for me (on Ubuntu 17.10)
    – steeldriver
    Mar 6 at 1:22











  • @steeldriver Would you like to add it as an answer? It really worked, as it states in the answer you provide: Basically, it increases the limits on the scratch space in memory allocated to a thread.
    – Joshua Salazar
    Mar 7 at 3:21






  • 1




    @JoshuaSalazar please go ahead and write an answer yourself - you probably have a better understanding of the solution than me
    – steeldriver
    Mar 7 at 23:49
















  • It looks like it compiled OK but one of the post-compilation tests failed. did you examine the znep.out file? There may be more details near the end of that - hopefully some kind of error message about what the problem is. BTW, gpaw is packaged for ubuntu & kubuntu - why not just run sudo apt-get install gpaw gpaw-data?
    – cas
    Mar 6 at 1:05






  • 1




    Don't ask me to explain why, but setting ulimit -s unlimited as discussed here Install CLAPACK-3.2.1 in fedora 23 appears to get past this error for me (on Ubuntu 17.10)
    – steeldriver
    Mar 6 at 1:22











  • @steeldriver Would you like to add it as an answer? It really worked, as it states in the answer you provide: Basically, it increases the limits on the scratch space in memory allocated to a thread.
    – Joshua Salazar
    Mar 7 at 3:21






  • 1




    @JoshuaSalazar please go ahead and write an answer yourself - you probably have a better understanding of the solution than me
    – steeldriver
    Mar 7 at 23:49















It looks like it compiled OK but one of the post-compilation tests failed. did you examine the znep.out file? There may be more details near the end of that - hopefully some kind of error message about what the problem is. BTW, gpaw is packaged for ubuntu & kubuntu - why not just run sudo apt-get install gpaw gpaw-data?
– cas
Mar 6 at 1:05




It looks like it compiled OK but one of the post-compilation tests failed. did you examine the znep.out file? There may be more details near the end of that - hopefully some kind of error message about what the problem is. BTW, gpaw is packaged for ubuntu & kubuntu - why not just run sudo apt-get install gpaw gpaw-data?
– cas
Mar 6 at 1:05




1




1




Don't ask me to explain why, but setting ulimit -s unlimited as discussed here Install CLAPACK-3.2.1 in fedora 23 appears to get past this error for me (on Ubuntu 17.10)
– steeldriver
Mar 6 at 1:22





Don't ask me to explain why, but setting ulimit -s unlimited as discussed here Install CLAPACK-3.2.1 in fedora 23 appears to get past this error for me (on Ubuntu 17.10)
– steeldriver
Mar 6 at 1:22













@steeldriver Would you like to add it as an answer? It really worked, as it states in the answer you provide: Basically, it increases the limits on the scratch space in memory allocated to a thread.
– Joshua Salazar
Mar 7 at 3:21




@steeldriver Would you like to add it as an answer? It really worked, as it states in the answer you provide: Basically, it increases the limits on the scratch space in memory allocated to a thread.
– Joshua Salazar
Mar 7 at 3:21




1




1




@JoshuaSalazar please go ahead and write an answer yourself - you probably have a better understanding of the solution than me
– steeldriver
Mar 7 at 23:49




@JoshuaSalazar please go ahead and write an answer yourself - you probably have a better understanding of the solution than me
– steeldriver
Mar 7 at 23:49










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










After attending to a HPC lecture and doing some research I had the answer.



It looks like the kernel associates a certain amount of memory to the compilation processes. This feature helps in some cases, when bugs can arise and those start to allocate unnecessarily big amounts of memory. But sometimes, the compilation requires more memory than usual and start getting errors.



Then, by using the following command, it sets an unlimited amount of memory to the compilation.



ulimit -s unlimited


Now everything works fine.



Thanks to @steeldriver for the extra questions.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428394%2flapack-make-fails-recipe-for-target-znep-out-failed-error%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote



    accepted










    After attending to a HPC lecture and doing some research I had the answer.



    It looks like the kernel associates a certain amount of memory to the compilation processes. This feature helps in some cases, when bugs can arise and those start to allocate unnecessarily big amounts of memory. But sometimes, the compilation requires more memory than usual and start getting errors.



    Then, by using the following command, it sets an unlimited amount of memory to the compilation.



    ulimit -s unlimited


    Now everything works fine.



    Thanks to @steeldriver for the extra questions.






    share|improve this answer
























      up vote
      1
      down vote



      accepted










      After attending to a HPC lecture and doing some research I had the answer.



      It looks like the kernel associates a certain amount of memory to the compilation processes. This feature helps in some cases, when bugs can arise and those start to allocate unnecessarily big amounts of memory. But sometimes, the compilation requires more memory than usual and start getting errors.



      Then, by using the following command, it sets an unlimited amount of memory to the compilation.



      ulimit -s unlimited


      Now everything works fine.



      Thanks to @steeldriver for the extra questions.






      share|improve this answer






















        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        After attending to a HPC lecture and doing some research I had the answer.



        It looks like the kernel associates a certain amount of memory to the compilation processes. This feature helps in some cases, when bugs can arise and those start to allocate unnecessarily big amounts of memory. But sometimes, the compilation requires more memory than usual and start getting errors.



        Then, by using the following command, it sets an unlimited amount of memory to the compilation.



        ulimit -s unlimited


        Now everything works fine.



        Thanks to @steeldriver for the extra questions.






        share|improve this answer












        After attending to a HPC lecture and doing some research I had the answer.



        It looks like the kernel associates a certain amount of memory to the compilation processes. This feature helps in some cases, when bugs can arise and those start to allocate unnecessarily big amounts of memory. But sometimes, the compilation requires more memory than usual and start getting errors.



        Then, by using the following command, it sets an unlimited amount of memory to the compilation.



        ulimit -s unlimited


        Now everything works fine.



        Thanks to @steeldriver for the extra questions.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 14 at 3:19









        Joshua Salazar

        190112




        190112






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428394%2flapack-make-fails-recipe-for-target-znep-out-failed-error%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay