Abinit-6.12.1 make problem

option, parallelism,...

Moderators: fgoudreault, mcote

Forum rules
Please have a look at ~abinit/doc/config/build-config.ac in the source package for detailed and up-to-date information about the configuration of Abinit 8 builds.
For a video explanation on how to build Abinit 7.x for Linux, please go to: http://www.youtube.com/watch?v=DppLQ-KQA68.
IMPORTANT: when an answer solves your problem, please check the little green V-like button on its upper-right corner to accept it.
Locked
longwood
Posts: 1
Joined: Tue Mar 13, 2012 4:49 am

Abinit-6.12.1 make problem

Post by longwood » Tue Mar 13, 2012 4:57 am

Dear all, I meet the following problems,

configure: error: in `/home/ld/software/abinit/abinit-6.12.1/fallbacks/sources/etsf_io-1.0.4':
configure: error: Fortran compiler cannot create executables
See `config.log' for more details.
make[3]: *** [stamps/etsf_io-config-stamp] Error 77
make[3]: Leaving directory `/home/longwood/software/abinit/abinit-6.12.1/fallbacks'
make[2]: [all-local] Error 2 (ignored)
Checking build of etsf_io fallback
test -e stamps/etsf_io-install-stamp
make[2]: *** [all-local] Error 1
make[2]: Leaving directory `/home/longwood/software/abinit/abinit-6.12.1/fallbacks'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/longwood/software/abinit/abinit-6.12.1'
make: *** [all] Error 2

I checked the config.log in /fallbacks, and I found:
gcc version 4.6.2 (SUSE Linux)
configure:3756: $? = 0
configure:3745: gcc -V >&5
gcc: error: unrecognized option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:3756: $? = 1
configure:3745: gcc -qversion >&5
gcc: error: unrecognized option '-qversion'
gcc: fatal error: no input files
compilation terminated.

After I change gcc to ifort, it neglected the unrecognized option '-V', but the error no input files is still there.

Thanks.

User avatar
pouillon
Posts: 651
Joined: Wed Aug 19, 2009 10:08 am
Location: Spain
Contact:

Re: Abinit-6.12.1 make problem

Post by pouillon » Tue Mar 13, 2012 4:25 pm

These failures are perfectly normal, since each compiler has its own way of providing its version.

What you have to look for is the last occurence of the word "failed" in config.log. It is the one which will tell you why your build fails.
Yann Pouillon
Simune Atomistics
Donostia-San Sebastián, Spain

Locked