COAWST compiling Problem

[changjw214]

Hi friends-
I'm trying to compile COAWST(ROMS-SWAN coupling).
so
1. I compiled MCT which is in COAWST trunk with gfortran
and I got lib, include directories.
2. I set my own cpps in header file (attached)
3. In order to compile COAWST, change Linux-pgi.mk in trunk (using pgi)
4. Change build.bash

But I have error like this

cd /local/home/jchang/Sed_Coawst/Coupling/Build; /usr/vimssw/pgi/mpich/bin/mpif90 -c -fastsse -Mipa=fast -tp k8-64 -I/local/home/jchang/include mp_exchange.f90
PGF90-S-0038-Symbol, mpi_proc_null, has not been explicitly declared (mp_exchange.f90)
0 inform, 0 warnings, 1 severes, 0 fatal for tile_neighbors
make: *** [/local/home/jchang/Sed_Coawst/Coupling/Build/mp_exchange.o] Error 2

Is anyone who have an idea about it??
(I attach Linux-pgi.mk, buildM.bash, header file)

[jcwarner]

this is an issue during the build of roms. looks like an mpi could not find a correct lib or something. Can you build an application with just roms? this might be an openmpi problem.

[changjw214]

Thanks for response-

Before this trial, I use just ROMS only.
But I wanna do coupling ROMS & SWAN in this trial.
When I was in just ROMS only, this mpich path didn't give errors and complete compiling.
So
1. When I am coupling, Should I use openmpi instead of mpich?

2. Does it have any possibility of wrong compiling of MCT?

[jcwarner]

the problem you are showing is roms code compilation. the coupling would have nothing to do with this. So if you can get roms to compile by itself, then use those same mpi settings to compile the coupled system.

[changjw214]

Sorry, I'm still confused with this.
When I turn off SWAN_MODEL, MCT_LIB in my header file,
I can compile ROMS ONLY with same mpi path(lib, include).
But if I just define SWAN_MODEL & MCT_LIB, it can't(No change in other things).

[jcwarner]

In ROMS/Utility/mp_exchange.F the only occurrence of mpi_proc_null is on lines 113-117 as:
# if defined MPI
Null_Value=MPI_PROC_NULL
# else
Null_Value=-1
# endif

so if you defined MPI to compile roms only, and defined MPI to compile roms+swan, then this section of code
Null_Value=MPI_PROC_NULL
should be active both times and there should be no difference in the code.
There is no effect here for the coupling.

Look at the Build/mp_exchange.f90 files. they should be the same.
-john