Yambo Community Forum

Hello,

Using Intel 2017 as my compiler and SGIMPT 2.18 as my MPI stack, it seems like 'configure' gets confused.

At the end, it shows::

# - COMPILERS -
#
# FC kind = gfortran GNU Fortran (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
# MPI kind= Intel(R) MPI Library 2017 Update 1 for Linux* OS
#
# [ CPP ] icc -E -ansi -D_MPI -D_FFTW -D_TIMING
# [ FPP ] gfortran -E -P -cpp -D_MPI -D_FFTW -D_TIMING -D_MPI -D_FFTW -D_TIMING
# [ CC ] mpiicc -O2 -D_C_US -D_FORTRAN_US
# [ FC ] mpiifort -O3 -g -mtune=native
# [ FCUF] -O0 -g -mtune=native
# [ F77 ] mpiifort -O3 -g -mtune=native
# [ F77U] -O0 -g -mtune=native
# [Cmain]
#

I don't want it to use the system's gfortran (which is ancient as you can see) but I want it to use the proper intel fortran pre-processor

when I configure with "configure FPP=ifort" I get errors, so I'm missing something. Is there a better way to set it?

Thank you.

Dear andrew.downs ,
please sign your post with your name and affiliation, you can do once for all by filling your signature in the user profile of the forum.
It seems that something is not set properly in your path. What it does worry is .
What happens if you specify directly the fortran preprocessor as: or alternatively: If it fails to recognize it, please post the config.log file.

Best,
Daniele

Daniele,

FPP="fpp -free -P" results in the same behavior as not setting FPP

FPP="ifort -fpp" results in an error:

checking fortran 90 modules inclusion flag... -I
configure: testing C-preprocessor icc -E -ansi
checking if C precompiler works on C source... yes
configure: testing FC-preprocessor ifort -fpp
checking if FC precompiler works on FC source... no
configure: error: Found FC precompiler problems in processing FC source.



I looked at my $PATH and 'ifort' is in my path before gfortran is, but both are available. The gfortran Yambo is finding is the -really- old one that's built into the base-system. Is there a way to tell Yambo to ignore gfortran entirely? Is gfortran required?

Thank you

Dear Andrew,
can you please post your config.log file?

Daniele