Forum_general

General

At this page you can post questions or start discussions on general topics related to Delft3D Flexible Mesh.

Please select a proper category below (if possible), to post your message or reply to an existing post. Please add tags to your posts to simplify searching.

 

** PLEASE TAG YOUR POST! **

 

 

 

 


Message Boards

Between ifort - gfortran - mpif90 for DFM compilation in LINUX

Santosa Putra, modified 6 Years ago.

Between ifort - gfortran - mpif90 for DFM compilation in LINUX

Youngling Posts: 0 Join Date: 9/16/13 Recent Posts
First of all I would like to greet : "Happy New Year 2014" , wish you success in this year.

In the tutorial page (http://publicwiki.deltares.nl/display/DFLOWFM/Building+on+Linux), it was stated that we should use similar compiler during the installation.

If I want to compile DFM for MPI, shall i use mpif90 since the beginning to compile NETCDF, PETSC, METIS, etc. ? (because I will compile DFM using mpif90)

Thanks
Santosa Putra, modified 5 Years ago.

RE: Between ifort - gfortran - mpif90 for DFM compilation in LINUX (Answer)

Youngling Posts: 0 Join Date: 9/16/13 Recent Posts
In my opinion all those compiler have the the same function. However, during the compiling process, we should be consistent and follow the procedure stated in the tutorial.

However, if you use ifort, when you move the installed system to another computer, you have to adjust and set the ifort license in the new computer.

Good day emoticon :smile:
Arthur van Dam, modified 5 Years ago.

RE: Between ifort - gfortran - mpif90 for DFM compilation in LINUX

Youngling Posts: 17 Join Date: 3/3/11 Recent Posts
Just for completeness:
What is beyond the scope of the D-Flow FM build instructions:
* compiler license issues
* compiler paths/settings (We mention the well-known ifortvars.sh as an example only.
* mpi flavours (although we do share some experience with versions)

We do strive to specify library versions, so what is in the scope:
* third-party libraries, such as NetCDF and PETSc.
* build steps/order

Moving installations to another machine is possible, but not recommended nor strongly supported, because of all the dependent libraries: the machine on which you built the software may have other system or compiler libraries than the target system that you're copying the software to.