make target_name error

If you are a new user, please take a look at this thread. All questions related to the download of the COHERENS code, the installation and how to run the pre-installed test cases are to be posted here. Experienced users are also encouraged to take a look at this forum to help newbies.

Moderator: Katrijn

Post Reply
mfaismail
Posts: 1
Joined: Tue Oct 24, 2017 1:58 am
Full name: James Ibrohim

make target_name error

Post by mfaismail »

Dear Katrijn,

Hi, I m a beginner in using an ocean model and I would like your help in the beginning process of installing the COHERENS into the HPC at the university. By the way, I am in the process to test if the COHERENS compilation works fine (please see the image below):
Error_1.png
Error_1.png (23.17 KiB) Viewed 43889 times
I am having message of "No such file or directory" after I type "make linux-gfort", Is there any more step do I need to edit or should I rename the objects.cmp to objects_part.cmp and dependencies.cmp to dependencies_part.cmp ?

Thank you.

Best regards,
mfaismail
Katrijn
Posts: 87
Joined: Fri Nov 29, 2013 3:04 pm
Full name: Katrijn Baetens

Re: make target_name error

Post by Katrijn »

Hi Mfaismail,
Can you mail me again a pm?
Cheers,
Katrijn
Sou
Posts: 51
Joined: Wed Sep 03, 2014 7:46 pm
Full name: Soudeh Afsharian

Re: make target_name error

Post by Sou »

I got the same error in installing V2.11



make linux-gfort
Makefile:69: /comps/objects_part.cmp: No such file or directory
Makefile:90: /comps/dependencies_part.cmp: No such file or directory
make: Warning: File `COHERENS/code/biology_default/comps/dependencies_bio.cmp' has modification time 2e+08 s in the future
make: *** No rule to make target `/comps/dependencies_part.cmp'. Stop.



Could you please let us know what we should do with this error?
Thank you,
Sue
Katrijn
Posts: 87
Joined: Fri Nov 29, 2013 3:04 pm
Full name: Katrijn Baetens

Re: make target_name error

Post by Katrijn »

Hi Soudeh,
An mistake has entered the coherensflags.cmp file of the on-line version. Please replace the following line in this file:

PARMOD = COHERENS/code/tracers

by

PARMOD = COHERENS/code/tracers_default

Please let me know how it works,
Katrijn
Sou
Posts: 51
Joined: Wed Sep 03, 2014 7:46 pm
Full name: Soudeh Afsharian

Re: make target_name error

Post by Sou »

Thank you, now it shows this error:
make: Warning: File `COHERENS/code/tracers_default/comps/dependencies_part.cmp' has modification time 2e+08 s in the future
make coherens "FC=gfortran" "FCOPTS= -O3" "FCDEFS=" \
"FCDEBUG=" "CPP=" "CPPF=cpp" "CPPOPTS=-traditional-cpp" \
"CPPDEFS=-DALLOC -DCDF"
make[1]: Entering directory `/home/Desktop/v2.11/test 2.11.2'
make[1]: Warning: File `COHERENS/code/tracers_default/comps/dependencies_part.cmp' has modification time 2e+08 s in the future
cpp -traditional-cpp -DALLOC -DCDF COHERENS/code/physics/source/couplingvars.F90 ./couplingvars.f90
gfortran -c ./couplingvars.f90 -o couplingvars.o
gfortran -c COHERENS/code/physics/source/currents.f90 -o currents.o
gfortran -c COHERENS/code/physics/source/syspars.f90 -o syspars.o
gfortran -c COHERENS/code/physics/source/datatypes.f90 -o datatypes.o
gfortran -c COHERENS/code/physics/source/density.f90 -o density.o
gfortran -c COHERENS/code/physics/source/depths.f90 -o depths.o
gfortran -c COHERENS/code/physics/source/diffusion.f90 -o diffusion.o
gfortran -c COHERENS/code/physics/source/fluxes.f90 -o fluxes.o
gfortran -c COHERENS/code/physics/source/grid.f90 -o grid.o
gfortran -c COHERENS/code/physics/source/gridpars.f90 -o gridpars.o
gfortran -c COHERENS/code/physics/source/iopars.f90 -o iopars.o
gfortran -c COHERENS/code/physics/source/meteo.f90 -o meteo.o
gfortran -c COHERENS/code/physics/source/modids.f90 -o modids.o
gfortran -c COHERENS/code/physics/source/multigrid.f90 -o multigrid.o
gfortran -c COHERENS/code/physics/source/nestgrids.f90 -o nestgrids.o
gfortran -c COHERENS/code/physics/source/obconds.f90 -o obconds.o
gfortran -c COHERENS/code/physics/source/optics.f90 -o optics.o
gfortran -c COHERENS/code/physics/source/paralpars.f90 -o paralpars.o
gfortran -c COHERENS/code/physics/source/physpars.f90 -o physpars.o
gfortran -c COHERENS/code/physics/source/relaxation.f90 -o relaxation.o
gfortran -c COHERENS/code/physics/source/structures.f90 -o structures.o
gfortran -c COHERENS/code/physics/source/switches.f90 -o switches.o
gfortran -c COHERENS/code/physics/source/tide.f90 -o tide.o
gfortran -c COHERENS/code/physics/source/timepars.f90 -o timepars.o
gfortran -c COHERENS/code/physics/source/turbpars.f90 -o turbpars.o
gfortran -c COHERENS/code/physics/source/turbulence.f90 -o turbulence.o
gfortran -c COHERENS/code/physics/source/wavepars.f90 -o wavepars.o
gfortran -c COHERENS/code/physics/source/wavevars.f90 -o wavevars.o
gfortran -c COHERENS/code/physics/source/utility_routines.f90 -o utility_routines.o
cpp -traditional-cpp -DALLOC -DCDF COHERENS/code/physics/source/error_routines.F90 ./error_routines.f90
gfortran -c ./error_routines.f90 -o error_routines.o
gfortran -c COHERENS/code/biology_default/source/biovars_routines.f90 -o biovars_routines.o
gfortran -c COHERENS/code/physics/source/datatypes_init.f90 -o datatypes_init.o
make[1]: *** No rule to make target `partids.f90', needed by `partids.o'. Stop.
make[1]: Leaving directory `/home/Desktop/v2.11/test 2.11.2'
make: *** [linux-gfort] Error 2
Katrijn
Posts: 87
Joined: Fri Nov 29, 2013 3:04 pm
Full name: Katrijn Baetens

Re: make target_name error

Post by Katrijn »

Dear Soudeh,
Can you check if you are working with the latest code and not a mixture of several codes? Can you test if you start from scratch in a different directory you get the same error? Meanwhile, I am trying to reproduce this error.
Kind regards,
Katrijn
Sou
Posts: 51
Joined: Wed Sep 03, 2014 7:46 pm
Full name: Soudeh Afsharian

Re: make target_name error

Post by Sou »

in a new directory I even get an error one step before compiling:

sudo: unable to execute COHERENS/install_test: No such file or directory
Katrijn
Posts: 87
Joined: Fri Nov 29, 2013 3:04 pm
Full name: Katrijn Baetens

Re: make target_name error

Post by Katrijn »

Dear Soudeh,
I tried to follow the actions of an external user and so far I was able to run the river test case without any problems. Can you tell me the protocoll you are following?
Best regards,
Katrijn
Post Reply