Page 1 of 1

problem of compiling abinit-7.4.2 on linux

Posted: Mon Oct 14, 2013 9:12 pm
by tzeng
Dear Colleagues,

I am completely new to abinit and I am trying to compile abinit-7.4.2 on our linux cluster but run into a problem. I wish I could get your help out of this.

Here is some information about my computer.

Operating system: Rocks 6.0 with CentOS 6.2
Each compute node:
32GB of RAM, 883GB /tmp
12 core, Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz

I simply downloaded the source package of 7.4.2 and followed the installation note online (http://www.abinit.org/documentation/hel ... stall.html)

My config.log is attached.

config.log
(108.41 KiB) Downloaded 318 times


When I `make`, I have the following error message:

(astra)abinit-7.4.2[1173] make
make all-recursive
make[1]: Entering directory `/home/fs01/tz265/LOCAL/abinit-7.4.2'
Making all in fallbacks
make[2]: Entering directory `/home/fs01/tz265/LOCAL/abinit-7.4.2/fallbacks'
cd . && /bin/sh /home/fs01/tz265/LOCAL/abinit-7.4.2/fallbacks/config/gnu/missing --run automake-1.11 --gnu
Makefile.am:47: DO_BUILD_FOX does not appear in AM_CONDITIONAL
Makefile.am:115: DO_BUILD_LIBXC does not appear in AM_CONDITIONAL
Makefile.am:184: DO_BUILD_LINALG does not appear in AM_CONDITIONAL
Makefile.am:251: DO_BUILD_NETCDF does not appear in AM_CONDITIONAL
Makefile.am:321: DO_BUILD_ATOMPAW does not appear in AM_CONDITIONAL
Makefile.am:389: DO_BUILD_ETSF_IO does not appear in AM_CONDITIONAL
Makefile.am:457: DO_BUILD_WANNIER90 does not appear in AM_CONDITIONAL
Makefile.am:525: DO_BUILD_BIGDFT does not appear in AM_CONDITIONAL
make[2]: *** [Makefile.in] Error 1
make[2]: Leaving directory `/home/fs01/tz265/LOCAL/abinit-7.4.2/fallbacks'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/fs01/tz265/LOCAL/abinit-7.4.2'
make: *** [all] Error 2

It seems I didn't configure correctly for fallback. I would deeply appreciate if any of you could tell me what I could do to solve this problem.

All my best,

Toby

Re: problem of compiling abinit-7.4.2 on linux

Posted: Tue Oct 22, 2013 12:22 pm
by pouillon
You probably have a timestamp problem related to your disk storage installation. Please consult your system administrator regarding this issue.

In the meantime, you may try to unpack Abinit preserving the file timestamps by using the --atime-preserve option of tar, or the equivalent option of your preferred archive manager.