[MITgcm-support] MITgcm on BCp2: domain decomposition

[Yuan Lian]

Is there any particular reason you don't want to add the include path to 
your optfile,
e.g. linux_amd64_gfortran? It is very common that one needs to modify 
the optfile depending
on the system configuration of the compilers etc.

Yuan


On 12/13/11 3:24 AM, Fanny Monteiro wrote:
> Hi,
>
>    I have been compiling and running on parallel processors the MITgcm 
> on the HPC of the University Bristol (BlueCrystal Phase 2).
>
> We had to make a few changes and I am wondering if anyone has an idea 
> of a better way of doing it (especially in relation to point 3).
>
> Here are the changes that our IT specialist needed to make in order to 
> get genmake2 to run without warnings and the model to compile:
>
> *1.* Set the environment variable NETCDF_ROOT.  That's fine.
>
> *2.* In the optfile, add '-l netcdf' to the line:
>        LIBS="-L${NETCDF_ROOT}/lib -l netcdf"
> I would have thought everyone would have needed that.
> (I used linux_amd64_gfortran, but we see that, e.g. linux_ia64_ifort 
> would have required a similar edit.
>
> *3.* After getting my Makefile, I needed to add the include path to my 
> MPI headers:
>        INCLUDES = 
> -I/gpfs/cluster/geog/ggdagw/netcdf/4.0/gnu_fc_4.1.2/include 
> -I/usr/mpi/gcc/openmpi-1.4.2-
> qlc/include
> so that make depend would not give a warning about not finding "mpif.h"
>
> *4.* Then I could compile cleanly--without fixing (3), I'd get a 
> compile error.
>
> Thanks in advance for your help/comments.
> Cheers,
> Fanny
>
>
> -- 
> Dr Fanny M Monteiro
> Research Associate
> School of Geographical Sciences
> University of Bristol, Bristol BS8 1SS, UK
> Phone (+44) 117 33 18351
> Email f.monteiro at bristol.ac.uk <mailto:f.monteiro at bristol.ac.uk>
> Web https://sites.google.com/site/fmonteir/
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20111213/2f73d2e9/attachment.htm>