compile error for version 1.2

asked 2022-02-18 03:26:00 +0100

DJ
3

Hi,

I wonder if anyone has encountered the following error while compiling CROCO ver 1.2.

gmake: Circular oce_sed.mod <- oce_sed.o dependency dropped.
m2c -o oce_sed.o oce_sed.mod
gmake: m2c: Command not found
gmake: * [oce_sed.o] Error 127

It looks like the object file, ocean.sed.o is sediment transport module which I did not activate.

I tried to compile with some test cases including upwelling, but none of them worked. I did not have the same error for version 1.1, which works fine. I tried openmpi + gfortran and intel fortran + intelmpi and neither worked.

I wanted to ask on this forum before I start looking at the makefile.

Thanks in advance.

-DJ

edit retag flag offensive close merge delete

add a comment

0

answered 2022-11-04 18:45:27 +0100

andres

96

Hi, I ran into this also for v1.2.1 and gfortran

gfortran --version GNU Fortran (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)

gmake: Circular oce_sed.mod <- oce_sed.o dependency dropped.
m2c    -o oce_sed.o oce_sed.mod
gmake: m2c: Command not found
gmake: *** [oce_sed.o] Error 127

any update on a solution?

I found comments on other forums

https://lists.mcs.anl.gov/pipermail/p...

about doing this to solve the problem

You can override it by adding the following line to your makefile:

%.o: %.mod

but I am not sure where to apply it

edit flag offensive delete link

Comments

Hi It should be added in OCEAN/Makedefs.generic Rachid

Rachid ( 2022-11-05 16:09:35 +0100 )edit

Almost there... when I do that, the compilation advances a bit more and then I get /include pisces_ini_.f90 -o pisces_ini.o gmake: *** No rule to make target `oce_sed.o', needed by `croco'. Stop.

andres ( 2022-11-08 19:47:35 +0100 )edit

add a comment

0

answered 2022-02-18 17:29:43 +0100

Matthieu.C
1

Hello,

Did you check that the source path in your jobcomp is correct ? It should point to your "OCEAN" directory and make sure you have all the others directories of CROCO source code next to OCEAN. SOURCE=/home/test/croco/OCEAN

Matthieu

edit flag offensive delete link

Comments

Yes.

DJ ( 2022-02-18 22:36:44 +0100 )edit

add a comment

0

answered 2022-02-18 13:46:54 +0100

Rachid

106

Hi Just to make sure, can you just in your Run directory remove the Compile directory and re-launch jobcomp ? Rachid

edit flag offensive delete link

Comments

Thanks for your comment. That makes no difference. The same error. jobcomp and Makefile between v1.1 and v1.2 are similar and no red flags so far. I compared ver 1.1 and ver 1.2 compiling log and it looks like the error occurred when compiling CROCO was either pisces_ini or module_parameter_oa.F.

DJ ( 2022-02-18 15:01:44 +0100 )edit

add a comment