Compiling Error on Yambo-4.3.2

Having trouble compiling the Yambo source? Using an unusual architecture? Problems with the "configure" script? This is the place to look.

Moderators: Davide Sangalli, Daniele Varsano, andrea.ferretti, andrea marini, myrta gruning, Conor Hogan

Forum rules
If you have trouble compiling Yambo, please make sure to list:
(1) the compiler (vendor and release: e.g. intel 10.1)
(2) the architecture (e.g. 64-bit IBM SP5)
(3) if the problems occur compiling in serial/in parallel
(4) the version of Yambo (revision number/major release version)
(5) the relevant compiler error message
Post Reply
Longjun Xiang
Posts: 30
Joined: Tue May 07, 2019 9:53 am

Compiling Error on Yambo-4.3.2

Post by Longjun Xiang » Tue May 07, 2019 11:36 am

Dear Sir:

Following your instructions in README, I met a problem when I compile the latest version Yambo-4.3.2. For the first step (./configure), no errors appearred. For the second step (make all), the following ERROR information appearred:

compilation aborted for special_functions.c (code 4)
make[6]: *** [special_functions.lo] Error 1
make[6]: Leaving directory `/home/xianglj/software/yambo/yambo-4.3.2/lib/libxc/libxc-2.2.3/src'
make[5]: *** [all] Error 2
make[5]: Leaving directory `/home/xianglj/software/yambo/yambo-4.3.2/lib/libxc/libxc-2.2.3/src'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/xianglj/software/yambo/yambo-4.3.2/lib/libxc/libxc-2.2.3'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/xianglj/software/yambo/yambo-4.3.2/lib/libxc/libxc-2.2.3'
make[2]: *** [package-ready-stamp] Error 2
make[2]: Leaving directory `/home/xianglj/software/yambo/yambo-4.3.2/lib/libxc'
make[1]: *** [ext-libs] Error 2
make[1]: Leaving directory `/home/xianglj/software/yambo/yambo-4.3.2'
yambo build failed

For the first step: ./configure CC=icc FC=ifort F77=ifort MPICC=mpiicc MPIFC=mpiifort MPIF77=ifort --prefix=$HOME/software/yambo/4.3.1-icc15-impi5.0 --with-blas-libs="-L$MKLROOT/lib/intel64 -lmkl_intel_lp64 -lmkl_sequential -lmkl_core" -with-lapack-libs="-L$MKLROOT/lib/intel64 -lmkl_intel_lp64 -lmkl_sequential -lmkl_core" --with-blacs-libs="-L$MKLROOT/lib/intel64 -lmkl_blacs_intelmpi_lp64" --with-scalapack-libs="-L$MKLROOT/lib/intel64 -lmkl_scalapack_lp64" --with-iotk-path="/home/xianglj/QE/QE6.4.1/iotk"

The result is:

# FC kind = intel
# MPI kind= Intel(R) MPI Library 5.0 Update 3 for Linux* OS
# [ CPP ] icc -E -ansi -D_MPI -D_FFTW -D_SCALAPACK -D_TIMING
# [ FPP ] fpp -free -P -D_MPI -D_FFTW -D_SCALAPACK -D_TIMING
# [ CC ] mpiicc -O2 -D_C_US -D_FORTRAN_US
# [ FC ] mpiifort -assume bscc -O0 -ip
# [ FCUF] -assume bscc -O0
# [ F77 ] ifort -assume bscc -O0 -ip
# [ F77U] -assume bscc -O0
# [Cmain] -nofor_main

How can I fix this problem?

The problem has been solved by launching the server with a terminal, such as MobaXterm, on windows.

For completeness, the config.log is attached.
You do not have the required permissions to view the files attached to this post.
Dr. Longjun Xiang
School of Physical Science and Technology, ShanghaiTech University, China

Post Reply