1! -*- fortran -*- 2! 3! Copyright (c) 2004-2006 The Trustees of Indiana University and Indiana 4! University Research and Technology 5! Corporation. All rights reserved. 6! Copyright (c) 2004-2005 The University of Tennessee and The University 7! of Tennessee Research Foundation. All rights 8! reserved. 9! Copyright (c) 2004-2005 High Performance Computing Center Stuttgart, 10! University of Stuttgart. All rights reserved. 11! Copyright (c) 2004-2005 The Regents of the University of California. 12! All rights reserved. 13! Copyright (c) 2006-2014 Cisco Systems, Inc. All rights reserved. 14! Copyright (c) 2017 Research Organization for Information Science 15! and Technology (RIST). All rights reserved. 16! $COPYRIGHT$ 17! 18! Additional copyrights may follow 19! 20! $HEADER$ 21! 22!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 23! WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING 24!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 25! 26! Do ***not*** copy this file to the directory where your Fortran 27! fortran application is compiled unless it is absolutely necessary! Most 28! modern Fortran compilers now support the -I command line flag, which 29! tells the compiler where to find .h files (specifically, this one). For 30! example: 31! 32! shell$ mpifort foo.f -o foo -I$OMPI_HOME/include 33! 34! will probably do the trick (assuming that you have set OMPI_HOME 35! properly). 36! 37! That being said, OMPI's "mpifort" wrapper compiler should 38! automatically include the -I option for you. The following command 39! should be equivalent to the command listed above: 40! 41! shell$ mpifort foo.f -o foo 42! 43! You should not copy this file to your local directory because it is 44! possible that this file will be changed between versions of Open MPI. 45! Indeed, this mpif.h is incompatible with the mpif.f of other 46! implementations of MPI. Using this mpif.h with other implementations 47! of MPI, or with other versions of Open MPI will result in undefined 48! behavior (to include incorrect results, segmentation faults, 49! unexplainable "hanging" in your application, etc.). Always use the 50! -I command line option instead (or let mpifort do it for you). 51! 52!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 53! WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING 54!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 55 56 include 'mpif-config.h' 57 include 'mpif-constants.h' 58 include 'mpif-handles.h' 59 include 'mpif-io-constants.h' 60 include 'mpif-io-handles.h' 61 include 'mpif-externals.h' 62 include 'mpif-sentinels.h' 63 include 'mpif-sizeof.h' 64