This thread is locked.Only browsing is available.
Top Page > Browsing
OpenMX-3.7 installation problem on Fedora 17
Date: 2013/05/26 05:46
Name: surender   <surender_kumar@iitb.ac.in>

Dear Prof. Ozaki

I tried to install the latest version (3.7) of OpenMX on Fedora 17 (64 bit) and encountered the following error

neb.c:35:23: fatal error: mimic_omp.h: No such file or directory
compilation terminated.
make: *** [neb.o] Error 1

Its looks to me that 'neb.c' requires 'mimic_omp.h' but there is no such file in the current distribution. So please help me to solve the erro.

Thanks & regards
Surender
IIT Bombay, India
メンテ
Page: [1]

Re: OpenMX-3.7 installation problem on Fedora 17 ( No.1 )
Date: 2013/05/26 08:44
Name: T. Ozaki

Hi,

Could you consult the following thread?

http://www.openmx-square.org/forum/patio.cgi?mode=view&no=1501

Or do you want to disable the OpenMP parallelism?
In this case, your error message suggests that neb.c should be modified.

Regards,

TO
メンテ
Re: OpenMX-3.7 installation problem on Fedora 17 ( No.2 )
Date: 2013/05/27 21:56
Name: surender  <surender_kumar@iitb.ac.in>

Dear Prof. Ozaki

Thanks for the help... and yes I do want to disable OpenMP... by the way the recently released patch solves my problem.

Thanks & regards,
Surender
メンテ
Re: OpenMX-3.7 installation problem on Fedora 17 ( No.3 )
Date: 2013/06/14 22:32
Name: surender  <surender_kumar@iitb.ac.in>

Dear Prof. Ozaki,

I need some clarification on "How OpenMP is implemented in OpenMX". Let us say if I want to compile the code WITH OUT OpenMP then I have to add -Dnoomp in CC and FC plus I have to apply the Patch-3.7.3 also, am I correct?

I added -Dnoomp to both CC and FC, also apply the Patch-3.7.3, but still I was not able to compile the code. Following were the error messages I received

============
openmx.o: In function `main':
openmx.c:(.text.startup+0x16b): undefined reference to `omp_set_num_threads'
truncation.o: In function `Set_RMI':
truncation.c:(.text+0x2a4): undefined reference to `omp_get_thread_num'
truncation.c:(.text+0x2ae): undefined reference to `omp_get_num_threads'
truncation.c:(.text+0x2ba): undefined reference to `omp_get_num_procs'
truncation.o: In function `Estimate_Trn_System':
truncation.c:(.text+0x749): undefined reference to `omp_get_thread_num'
truncation.c:(.text+0x751): undefined reference to `omp_get_num_threads'
truncation.c:(.text+0x761): undefined reference to `omp_get_num_procs'

..... many more similar errors related to OpenMP

============
elpa1.o: In function `__elpa1_MOD_invert_trm_complex':
elpa1.f90:(.text+0x10b7): undefined reference to `mpi_comm_rank_'
elpa1.f90:(.text+0x10d6): undefined reference to `mpi_comm_size_'
elpa1.f90:(.text+0x10f2): undefined reference to `mpi_comm_rank_'
elpa1.f90:(.text+0x110e): undefined reference to `mpi_comm_size_'
elpa1.f90:(.text+0x1896): undefined reference to `mpi_bcast_'
elpa1.f90:(.text+0x1941): undefined reference to `mpi_bcast_'
elpa1.f90:(.text+0x1ae8): undefined reference to `mpi_bcast_'

.... many more similar errors related to MPI

============
/opt/lapack/gcc/lib/liblapack.a(dlaed0.o): In function `dlaed0_':
dlaed0.f:(.text+0x30d): undefined reference to `_gfortran_pow_i4_i4'
dlaed0.f:(.text+0x331): undefined reference to `_gfortran_pow_i4_i4'
/opt/lapack/gcc/lib/liblapack.a(dlaed7.o): In function `dlaed7_':
dlaed7.f:(.text+0x177): undefined reference to `_gfortran_pow_i4_i4'
dlaed7.f:(.text+0x19f): undefined reference to `_gfortran_pow_i4_i4'
/opt/lapack/gcc/lib/liblapack.a(dlaeda.o): In function `dlaeda_':
dlaeda.f:(.text+0x80): undefined reference to `_gfortran_pow_i4_i4'
/opt/lapack/gcc/lib/liblapack.a(dlaeda.o):dlaeda.f:(.text+0x91): more undefined references to `_gfortran_pow_i4_i4' follow

... many more similar errors related to gfortran runtime library

============

MPI related errors were solved by adding -lmpi_f77 -lmpi_f90 to LIB
http://www.openmx-square.org/forum/patio.cgi?mode=view&no=1501

Adding -lgfortran to LIB, solves the gfortran related errors.
http://www.ncl.ucar.edu/Support/talk_archives/2012/2009.html
https://lists.tacc.utexas.edu/pipermail/gotoblas/2011-September/000747.html

Now I am left with OpenMP related errors. Here is my question if I add -fopenmp to both CC and FC, I can solve the OpenMP related errors, but then it means I have compiled the code with OpenMP (which I don't want, simply because I am not comfortable with it). So please help me to compile OpenMX ONLY with MPI.

One more thing what the flag -lg2c or -lgfortran does? Out of curiosity, I compiled the code WITH OUT -lg2c and it compiles with out any errors?

Surender



メンテ
Re: OpenMX-3.7 installation problem on Fedora 17 ( No.4 )
Date: 2013/06/16 11:28
Name: T. Ozaki

Hi,

> Here is my question if I add -fopenmp to both CC and FC, I can solve the OpenMP related
> errors, but then it means I have compiled the code with OpenMP (which I don't want, simply
> because I am not comfortable with it). So please help me to compile OpenMX ONLY with MPI.

The code compiled with -fopenmp can be used in either the flat MPI mode or the hybrid mode.
What is your purpose to compile the code without adding -fopenmp?
Also, I am wondering that the compilation without adding -fopenmp can produce the
executable file even if you have many error messages. Then, the executable file can be used
for the flat MPI calculation.

> One more thing what the flag -lg2c or -lgfortran does? Out of curiosity, I compiled the
> code WITH OUT -lg2c and it compiles with out any errors?

libg2c includes built-in functions of g77 in linux environment. Perhaps, the other libraries
you included have already included those functions.


Regards,

TO
メンテ
Re: OpenMX-3.7 installation problem on Fedora 17 ( No.5 )
Date: 2013/06/17 02:19
Name: Surender  <surender_kumar@iitb.ac.in>

Dear Prof. Ozaki

> Also, I am wondering that the compilation without adding -fopenmp can produce the
> executable file even if you have many error messages

No, it does not produce executable ( if any of the above mentioned error message appears).

Actually to get the executable, I have to get rid of
1.) OpenMP related errors
2.) MPI related errors
3.) GFORTRAN related errors

Only when ALL of these errors are resolved, I get the executable.

> The code compiled with -fopenmp can be used in either the flat MPI mode or the hybrid mode.

You mean I don't have need to bother about OpenMP and can use the code in flat MPI mode by
mpirun -np 4 openmx input > output

> What is your purpose to compile the code without adding -fopenmp?

Actually I am not very familiar to OpenMP that's why .... otherwise NO special purpose.

It may be silly question to ask but is there a way to subscribe to the forum?

Thanks for the help,

Surender
メンテ
Re: OpenMX-3.7 installation problem on Fedora 17 ( No.6 )
Date: 2013/06/17 09:26
Name: T. Ozaki

Hi,

> You mean I don't have need to bother about OpenMP and can use the code in flat MPI mode by
> mpirun -np 4 openmx input > output

Yes, I did.

Regards,

TO
メンテ

Page: [1]