No Makefile generated on HPE SGI 8600

HPC, IBM, Mac OS, Windows, ...

Moderators: jbeuken, Jordan, gmatteo

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 builds.
For a video explanation on how to build Abinit 7 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 button on its upper-right corner to accept it.
Post Reply
duanx
Posts: 2
Joined: Thu Apr 01, 2021 11:30 pm

No Makefile generated on HPE SGI 8600

Post by duanx » Thu Apr 01, 2021 11:48 pm

Hello,

I could previously install 8.8.4 on our HPE SGI 8600 machines. When I tried to install the 9.4.1 version on it, I could not get the Makefile with following configure command:

../configure --prefix=/app/abinit/abinit-9.4.1 CC=mpicc FC=mpif90 --with-hdf5=no

I used either intel compiler/MPI of version 18.0.3.222 or gcc/gfortran 7.3.0 with mpt 2.20. The at the end of config.log file it shows:

"configure: exit 0"

Please advise.

Thanks.

User avatar
admin
Site Admin
Posts: 33
Joined: Thu Sep 17, 2009 9:49 am

Re: No Makefile generated on HPE SGI 8600

Post by admin » Fri Apr 02, 2021 4:19 pm

Hi,

hdf5/netcdf/libxc are mandatory with abinit 9.x

see : https://docs.abinit.org/installation/

jmb

duanx
Posts: 2
Joined: Thu Apr 01, 2021 11:30 pm

Re: No Makefile generated on HPE SGI 8600

Post by duanx » Mon Apr 05, 2021 6:40 pm

Thanks for the response.
I enabled HDF5 and now I have following errors (grepped from config.log)

grep error config.log
conftest.c(18): error #2379: cannot open source file "ac_nonexistent.h"
conftest.c(18): error #2379: cannot open source file "ac_nonexistent.h"
icpc: command line error: no files specified; for help type "icpc -help"
conftest.F(3): error #5082: Syntax error, found END-OF-STATEMENT when expecting one of: => = . [ % ( :
| /* Override any GCC internal prototype to avoid an error.
conftest.c(83): catastrophic error: cannot open source file "sys/malloc.h"
conftest.c(50): error #2379: cannot open source file "sys/malloc.h"
conftest.c(110): error: expected an expression
conftest.c(67): error: identifier "not" is undefined
conftest.c(67): error: expected a ";"
conftest.c(81): error: identifier "not" is undefined
conftest.c(81): error: expected a ";"
conftest.c(84): warning #12: parsing restarts here after previous syntax error
conftest.F90(3): error #6216: This length or width specifier has been incorrectly used in this context. [16]
conftest.F90(4): error #6684: This is an incorrect value for a kind type parameter in this context. [KIND]
conftest.F90(4): error #5078: Unrecognized token '\' skipped
conftest.F90(4): error #5082: Syntax error, found IDENTIFIER 'NEWLINE' when expecting one of: .EQV. .NEQV. .XOR. .OR. .AND. .LT. < .LE. <= .EQ. == .NE. /= .GT. > ...
conftest.c(89): catastrophic error: cannot open source file "numpy/arrayobject.h"
conftest.c(89): catastrophic error: cannot open source file "numpy/arrayobject.h"
conftest.F90(3): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [ELPA]
conftest.F90(4): error #6457: This derived type name has not been declared. [ELPA_T]
conftest.F90(6): error #6535: This variable or component must be of a derived or structure type. [E]
conftest.F90(6): error #6460: This is not a field name that is defined in the encompassing structure. [SET]
conftest.F90(3): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [ELPA1]
conftest.F90(3): error #7002: Error in opening the compiled module file. Check INCLUDE paths. [ELPA1]

User avatar
admin
Site Admin
Posts: 33
Joined: Thu Sep 17, 2009 9:49 am

Re: No Makefile generated on HPE SGI 8600

Post by admin » Fri Apr 09, 2021 2:37 pm

Hi,
grep error config.log
this "grep" is not useful at all: it is quite normal to find errors when configuring because the BS tests/checks all a series of features... ( see https://www.gnu.org/software/autoconf/ to understand how ./configure works )

To help you, I need some useful information:
  • the full command of your ./configure
  • the full output of the ./configure command

Post Reply