Yambo Community Forum

Hi all,
I need to compile yambo but I've got this error:
>>>[Making external_c]<<<
make[1]: Entering directory `/home/yambo/yambo-3.4.1-rev61/src/external_c'
ct_etime.c c_printing.c io.c stack.c ar: creating libexternal_c.a
make[1]: Leaving directory `/home/yambo/yambo-3.4.1-rev61/src/external_c'

>>>[Making modules]<<<
make[1]: Entering directory `/home/yambo/yambo-3.4.1-rev61/src/modules'
ifort: command line warning #10159: invalid argument for option '-m'
mod_pars.F ifort: command line warning #10159: invalid argument for option '-m'
mod_units.F ifort: command line warning #10159: invalid argument for option '-m'
mod_stderr.F ifort: command line warning #10159: invalid argument for option '-m'
mod_parallel.F ifort: command line warning #10159: invalid argument for option '-m'
mod_wrapper.F ifort: command line warning #10159: invalid argument for option '-m'
mod_fields.F ifort: command line warning #10159: invalid argument for option '-m'
mod_collision.F ifort: command line warning #10159: invalid argument for option '-m'
mod_drivers.F ifort: command line warning #10159: invalid argument for option '-m'
mod_FFT.F ifort: command line warning #10159: invalid argument for option '-m'
mod_timing.F ifort: command line warning #10159: invalid argument for option '-m'
mod_logo ifort: command line warning #10159: invalid argument for option '-m'
mod_com.F ifort: command line warning #10159: invalid argument for option '-m'
mod_memory.F ifort: command line warning #10159: invalid argument for option '-m'
mod_R_lattice.F ifort: command line warning #10159: invalid argument for option '-m'
mod_matrix_operate.F ifort: command line warning #10159: invalid argument for option '-m'
mod_D_lattice.F ifort: command line warning #10159: invalid argument for option '-m'
mod_frequency.F ifort: command line warning #10159: invalid argument for option '-m'
mod_vec_operate.F ifort: command line warning #10159: invalid argument for option '-m'
mod_electrons.F ifort: command line warning #10159: invalid argument for option '-m'
mod_wave_func.F ifort: command line warning #10159: invalid argument for option '-m'
mod_interfaces.F ifort: command line warning #10159: invalid argument for option '-m'
mod_interpolate.F ifort: command line warning #10159: invalid argument for option '-m'
mod_X.F ifort: command line warning #10159: invalid argument for option '-m'
mod_functions.F ifort: command line warning #10159: invalid argument for option '-m'
mod_zeros.F ifort: command line warning #10159: invalid argument for option '-m'
mod_pseudo.F ifort: command line warning #10159: invalid argument for option '-m'
mod_BS.F ifort: command line warning #10159: invalid argument for option '-m'
mod_QP.F ifort: command line warning #10159: invalid argument for option '-m'
mod_TDDFT.F ifort: command line warning #10159: invalid argument for option '-m'
mod_ACFDT.F ifort: command line warning #10159: invalid argument for option '-m'
mod_wf_distribute.F ifort: command line warning #10159: invalid argument for option '-m'
mod_IO.F ifort: command line warning #10159: invalid argument for option '-m'
mod_fragments.F ifort: command line warning #10159: invalid argument for option '-m'
mod_xc_functionals.f90(29): error #7013: This module file was not generated by any release of this compiler. [XC_F90_LIB_M]
use xc_f90_lib_m
-----^
mod_xc_functionals.f90(48): error #6457: This derived type name has not been declared. [XC_F90_POINTER_T]
type(xc_f90_pointer_t) :: conf
--------^
mod_xc_functionals.f90(49): error #6457: This derived type name has not been declared. [XC_F90_POINTER_T]
type(xc_f90_pointer_t) :: info
--------^
mod_xc_functionals.f90(82): error #7013: This module file was not generated by any release of this compiler. [XC_F90_TYPES_M]
use xc_f90_types_m
---------^
mod_xc_functionals.f90(89): error #6457: This derived type name has not been declared. [XC_F90_POINTER_T]
type(xc_f90_pointer_t) :: p,info
----------^
mod_xc_functionals.f90(94): error #6406: Conflicting attributes or multiple declaration of name. [XC_F90_FUNC_INIT]
call xc_f90_func_init(p,info,f(ixc)%id,nsp)
------------^
mod_xc_functionals.f90(95): error #6404: This name does not have a type, and must have an explicit type. [INFO]
call xc_f90_info_name(info,f(ixc)%name)
-----------------------------^
mod_xc_functionals.f90(96): error #6406: Conflicting attributes or multiple declaration of name. [XC_F90_INFO_FAMILY]
f(ixc)%family=xc_f90_info_family(info)
---------------------^
mod_xc_functionals.f90(97): error #6406: Conflicting attributes or multiple declaration of name. [XC_F90_INFO_KIND]
f(ixc)%kind=xc_f90_info_kind(info)
-------------------^
mod_xc_functionals.f90(100): error #6406: Conflicting attributes or multiple declaration of name. [XC_F90_INFO_FLAGS]
f(ixc)%flags=xc_f90_info_flags(info)
--------------------^
mod_xc_functionals.f90(101): error #6460: This is not a field name that is defined in the encompassing structure. [CONF]
f(ixc)%conf=p
--------------^
mod_xc_functionals.f90(101): error #6404: This name does not have a type, and must have an explicit type. [P]
f(ixc)%conf=p
-------------------^
mod_xc_functionals.f90(102): error #6460: This is not a field name that is defined in the encompassing structure. [INFO]
f(ixc)%info=info
--------------^
mod_xc_functionals.f90(83): error #6580: Name in only-list does not exist. [XC_F90_FUNC_INIT]
use xc_f90_lib_m, ONLY:xc_f90_func_init,xc_f90_info_family,&
----------------------------^
mod_xc_functionals.f90(83): error #6580: Name in only-list does not exist. [XC_F90_INFO_FAMILY]
use xc_f90_lib_m, ONLY:xc_f90_func_init,xc_f90_info_family,&
---------------------------------------------^
mod_xc_functionals.f90(84): error #6580: Name in only-list does not exist. [XC_F90_INFO_KIND]
xc_f90_info_kind,xc_f90_info_flags
----------^
mod_xc_functionals.f90(84): error #6580: Name in only-list does not exist. [XC_F90_INFO_FLAGS]
xc_f90_info_kind,xc_f90_info_flags
---------------------------^
mod_xc_functionals.f90(115): error #6404: This name does not have a type, and must have an explicit type. [XC_UNPOLARIZED]
call xc_setup_fnctl(f,functional,XC_UNPOLARIZED)
--------------------------------------^
compilation aborted for mod_xc_functionals.f90 (code 1)
make[1]: *** [mod_xc_functionals.o] Error 1
make[1]: Leaving directory `/home/yambo/yambo-3.4.1-rev61/src/modules'
make: *** [yambo] Error 2

Dear Vasp84,

First, let me ask you to fill your signature with your affiliation. This is a rule of the forum.
Next, in order to help you please post the config.log file or any other information that can help to spot the problem.
Best,

Daniele

My affiliation:
Jaret Qi
New Mexico State Uni.
------------------
I have not change anything of the config file:
What should I change, though?

Dear Jaret,
you can fill your signature in the user control panel.
The config.log file is generated whenever you run the configure script.
It contains information on your compilers, machine, options etc.

Best,
Daniele

Dear Jaret,

please have a look to this post which possibly can help you to solve the problem.
Best,
Daniele

I do not know when I should do make_clean,
I have attached my .log file, did u see it?

Jaret Qi
NMSU-USA
Ph.D-candidate

Dear Jaret,
just type:
rerun the configure script again and then
if you still have problem post again the config.log file and the config.log present in the ./lib/libxc/ directory.

Best,
Daniele

No success!
see the .log file please

Dear Jaret,
we will have a look to the log file.
Anyway, please sign your post with your affiliation. I already told you.
Moreover a little bit of politeness as "Dear Daniele" , "Dear users and developers" etc...at the beginning of the messages or some thanks for the time spent, will be really appreciated. If you browse the posts in this forum it is a common practice in this community considering that no one is payed for that.

Best,
Daniele

Hi. From the log I do not understand where the compilations stops.

What is the error message?

Andrea