The ABINIT Users Mailing List ( CLOSED )

["Leonardo, Artiz L." <leonardoal@missouri.edu>]

Indeed it does! I was playing with a bit of advantage, I am one of  
those guys that tries to use stuff without reading the manual and  
afterwards when nothing works I start reading :) So yes, the make  
crashes.

When I type  "make", mpif90 starts to compile several subroutines with  
NO problem. It is the first time that mpicc is called when it crashes.

MAKE:
...........
netcdf-3.6.3 has been uncompressed.
mkdir tmp
cd netcdf-3.6.3 && \
         CPP="/opt/mpich2-intel-11//bin/mpicc -E" \
         CPPFLAGS="-DNDEBUG -DpgiFortran" \
         CC="/opt/mpich2-intel-11//bin/mpicc" \
         CFLAGS="-g -O3 -fschedule-insns2 -march=nocona -mmmx -msse -msse2 - 
msse3 -mfpmath=sse " \
         CXX="/opt/mpich2-intel-11/bin/mpicxx" \
         CXXFLAGS="-g -O3 -fschedule-insns2 -march=nocona -mmmx -msse -msse2 
- 
msse3 -mfpmath=sse " \
         F77="/opt/mpich2-intel-11//bin/mpif90" \
         FFLAGS=" -g  -O2 -ip -no-prec-div" \
         F90="/opt/mpich2-intel-11//bin/mpif90" \
         F90FLAGS=" -g  -O2 -ip -no-prec-div" \
         FC="/opt/mpich2-intel-11//bin/mpif90" \
         FCFLAGS=" -g  -O2 -ip -no-prec-div" \
         ./configure \
          --prefix=/home/leonardoal/abinit-5.8.4/plugins/netcdf/tmp \
          --disable-cxx
configure: netCDF 3.6.3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
configure: checking user options
checking whether CXX is set to ''... no
checking whether FC is set to ''... no
checking whether F90 is set to ''... no
checking whether this is a netCDF-4.x build... no
checking whether netCDF extra tests should be run (developers only)...  
no
checking whether documentation is to be installed... no
checking whether Fortran compiler(s) should be tested during  
configure... yes
checking whether configure should try to set compiler flags... yes
checking whether FFIO will be used... no
checking whether to skip C++, F77, or F90 APIs if compiler is  
broken... yes
checking whether only the C library is desired... no
checking whether examples should be built... yes
checking whether F77 API is desired... yes
checking whether F90 API is desired... yes
checking whether fortran type sizes should be checked... yes
checking whether C API is desired... yes
checking where to get netCDF C-only library for separate fortran  
libraries...
checking whether CXX API is desired... no
checking whether v2 netCDF API should be built... yes
checking whether the ncgen/ncdump should be built... yes
checking whether large file (> 2GB) tests should be run... no
checking whether benchmaks should be run (experimental)... no
checking whether extreme numbers should be used in tests... yes
checking where to put large temp files if large file tests are run... .
checking whether a win32 DLL is desired... no
checking whether separate fortran libs are desired... no
configure: finding C compiler
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
make[4]: *** [configure-stamp] Error 77
make[4]: Leaving directory `/home/leonardoal/abinit-5.8.4/plugins/ 
netcdf'
make[3]: *** [package-ready] Error 2
make[3]: Leaving directory `/home/leonardoal/abinit-5.8.4/plugins/ 
netcdf'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/leonardoal/abinit-5.8.4/plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/leonardoal/abinit-5.8.4'
make: *** [all] Error 2

As, always... many thanks!

On Oct 20, 2009, at 3:50 PM, Alain Jacques wrote:

> well ... your configure step looks nice to me :-) It seems to go  
> through
> the tests and to produce the makefiles. Don't be surprised to find
> failed tests in a config.log, it is normal that some tests cases  
> produce
> errors. Does the configure ends with message lines saying that you can
> continue with make - make multi - make mj4 etc ... ? If yes, go on  
> with
> a plain "make" and if no, please show the fatal error message that
> appears on your terminal.
>
> Kind regards,
>
> Alain
>
>
> leonardoal@missouri.edu wrote:
>> Hi all,
>>
>> I am trying to compile abinit and I am incapable. I am pretty sure  
>> that is due
>> to my huge ignorance but after surfing the archive and googling  
>> during one week
>> I still did not have success.
>>
>> I am trying to compile it in a small cluster of 32 core using:
>>
>> 1- Rocks
>> 2- Intel 11.0 : ifor, icc, icpc
>> 3.- mpich2: mpif90, mpicc and mpicxx previously built with the  
>> above intel
>> serial compilers.
>>
>> ...
>