[MITgcm-devel] new computer

Jean-Michel Campin jmc at ocean.mit.edu
Mon Jan 9 12:27:44 EST 2012


Hi Martin,

I think it's a good idea to add the kind of "generic" MPI_INC_DIR etc ...
in this optfile. 
And you can safely remove (or may be, comment out) the -static option, 
since it's not the standard way (I only see it in this particular optfile: 
linux_ia64_ifort+mpi_altix_meinesz, and only commented out in 1 other 
amd64_ifort optfile) and, although this optfile was used for non-mpi 
built on columbia, the columbia mpi optfile does not have the -static
option.

Waiting for new testreport results !
Cheers,
Jean-Michel

On Mon, Jan 09, 2012 at 03:21:56PM +0100, Martin Losch wrote:
> Hi Jean-Michel,
> 
> we have a new platform that I could include into our testing scheme, it's an "SGI UV100" with Linux and ifort.
> 
> The closest build-options files is linux_ia64_ifort, but rather than adding a new build_options file, I'd like to use this generic files. I added some generic lines about MPI_INC_DIR (just as in e.g. linux_amd_gfortran), that I could check in. All works fine except for the ifort flag "-static":
> The mpi libraries on this sgi are only available as dynamic libraries, so that I cannot use the flag "-static". Do you have a good idea how I can still use this opt file or will I have to make a specific one for this machine?
> 
> 
> Martin
> 
> 



More information about the MITgcm-devel mailing list