1
1
openmpi/config/ompi_config_files.m4

65 строки
2.3 KiB
Plaintext
Исходник Обычный вид История

# -*- shell-script -*-
#
# Copyright (c) 2009-2020 Cisco Systems, Inc. All rights reserved
# Copyright (c) 2017-2018 Research Organization for Information Science
# and Technology (RIST). All rights reserved.
# Copyright (c) 2018 Los Alamos National Security, LLC. All rights
# reserved.
Fortran: Enable using `LOGICAL` parameter in MPI extensions. If a subroutine of the Fortran `use-mpi-f08` binding in an MPI extension have a `LOGICAL` parameter and no `TYPE(MPI_Status)` parameter, it needs to use the `mpi_ext` module and call its corresponding subroutine in the `mpif-h` directory, as explained in `ompi/mpi/fortran/use-mpi-f08/mpi-f-interfaces-bind.h`. However, as shown in the figure below, the required directories are dependent on each other, and "Can't open module file" error occurs at build time. ompi/mpiext/{extension name}/use-mpi-f08 A | | | | V ompi/mpi/fortran/use-mpi-f08 <--- ompi/mpi/fortran/mpiext (mpi_ext.mod) In order to solve this problem, change the configuration and the build order. - divide Fortran extension directory (`ompi/mpi/fortran/mpiext`) into the directories for `use-mpi` and for `use-mpi-08` - `ompi/mpi/fortran/mpiext-use-mpi` : for `use-mpi` (mpi_ext.mod) - `ompi/mpi/fortran/mpiext-use-mpi-f08` : for `use-mpi-08` (mpi_f08_ext.mod) - change to the following build order about Fortran `use-mpi` and `use-mpi-f08` bindings in `ompi` 1. mpi_ext bindings of MPI extensions (`mpiext/{extension name}/use-mpi` directory) 2. Fortran use-mpi (`mpi/fortran/use-mpi-[ignore-]tkr` directory) 3. Fortran extension for use-mpi (`mpi/fortran/mpiext-use-mpi` directory) 4. Fortran use-mpi-f08 modules only (`mpi/fortran/use-mpi-f08/mod` directory) 5. mpi_f08_ext bindings of MPI extensions (`mpiext/{extension name}/use-mpi-f08` directory) 6. Fortran use-mpi-f08 (`mpi/fortran/use-mpi-f08` directory) 7. Fortran extension for use-mpi-f08 (`mpi/fortran/mpiext-use-mpi-f08` directory) Signed-off-by: Kurita, Takehiro <fj6370fp@aa.jp.fujitsu.com>
2018-06-07 05:15:14 +03:00
# Copyright (c) 2018 FUJITSU LIMITED. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
AC_DEFUN([OMPI_CONFIG_FILES],[
AC_CONFIG_FILES([
ompi/Makefile
ompi/etc/Makefile
ompi/include/Makefile
ompi/include/mpif.h
ompi/include/mpif-config.h
ompi/datatype/Makefile
ompi/debuggers/Makefile
ompi/mpi/c/Makefile
ompi/mpi/c/profile/Makefile
ompi/mpi/fortran/base/Makefile
ompi/mpi/fortran/mpif-h/Makefile
ompi/mpi/fortran/mpif-h/profile/Makefile
ompi/mpi/fortran/use-mpi-tkr/Makefile
ompi/mpi/fortran/use-mpi-tkr/fortran_sizes.h
ompi/mpi/fortran/use-mpi-tkr/fortran_kinds.sh
ompi/mpi/fortran/use-mpi-ignore-tkr/Makefile
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-interfaces.h
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-file-interfaces.h
ompi/mpi/fortran/use-mpi-ignore-tkr/mpi-ignore-tkr-removed-interfaces.h
ompi/mpi/fortran/use-mpi-f08/Makefile
ompi/mpi/fortran/use-mpi-f08/base/Makefile
ompi/mpi/fortran/use-mpi-f08/bindings/Makefile
ompi/mpi/fortran/use-mpi-f08/mod/Makefile
Fortran: Enable using `LOGICAL` parameter in MPI extensions. If a subroutine of the Fortran `use-mpi-f08` binding in an MPI extension have a `LOGICAL` parameter and no `TYPE(MPI_Status)` parameter, it needs to use the `mpi_ext` module and call its corresponding subroutine in the `mpif-h` directory, as explained in `ompi/mpi/fortran/use-mpi-f08/mpi-f-interfaces-bind.h`. However, as shown in the figure below, the required directories are dependent on each other, and "Can't open module file" error occurs at build time. ompi/mpiext/{extension name}/use-mpi-f08 A | | | | V ompi/mpi/fortran/use-mpi-f08 <--- ompi/mpi/fortran/mpiext (mpi_ext.mod) In order to solve this problem, change the configuration and the build order. - divide Fortran extension directory (`ompi/mpi/fortran/mpiext`) into the directories for `use-mpi` and for `use-mpi-08` - `ompi/mpi/fortran/mpiext-use-mpi` : for `use-mpi` (mpi_ext.mod) - `ompi/mpi/fortran/mpiext-use-mpi-f08` : for `use-mpi-08` (mpi_f08_ext.mod) - change to the following build order about Fortran `use-mpi` and `use-mpi-f08` bindings in `ompi` 1. mpi_ext bindings of MPI extensions (`mpiext/{extension name}/use-mpi` directory) 2. Fortran use-mpi (`mpi/fortran/use-mpi-[ignore-]tkr` directory) 3. Fortran extension for use-mpi (`mpi/fortran/mpiext-use-mpi` directory) 4. Fortran use-mpi-f08 modules only (`mpi/fortran/use-mpi-f08/mod` directory) 5. mpi_f08_ext bindings of MPI extensions (`mpiext/{extension name}/use-mpi-f08` directory) 6. Fortran use-mpi-f08 (`mpi/fortran/use-mpi-f08` directory) 7. Fortran extension for use-mpi-f08 (`mpi/fortran/mpiext-use-mpi-f08` directory) Signed-off-by: Kurita, Takehiro <fj6370fp@aa.jp.fujitsu.com>
2018-06-07 05:15:14 +03:00
ompi/mpi/fortran/mpiext-use-mpi/Makefile
ompi/mpi/fortran/mpiext-use-mpi-f08/Makefile
ompi/mpi/tool/Makefile
ompi/mpi/tool/profile/Makefile
Add MPI_T.5 man page for Open MPI-specific info Also added infrastructure to have developers write man pages in Markdown (vs. nroff). Pandoc >=v1.12 is used to convert those Markdown files into actual nroff man pages. Dist tarballs will contain generated nroff man pages; we don't want to require users to have Pandoc installed. Anyone who builds Open MPI from a git clone will need to have Pandoc installed (similar to how we treat Flex). You can opt out of Open MPI's Pandoc-generated man pages by configuring Open MPI with --disable-man-pages. This will also disable "make dist" (i.e., "make dist" will error if you configured with --disable-man-pages). Also removed the stuff to re-generate man pages. This commit also: 1. Includes a new man page, written in Markdown (ompi/mpi/man/man5/MPI_T.5.md) that contains Open MPI-specific information about MPI_T. 2. Includes a converted ompi/mpi/man/man3/MPI_T_init_thread.3.md (from MPI_T_init_thread.3in -- i.e., nroff) just to show that Markdown can be used throughout the Open MPI code base for man pages. 3. Made the Makefiles in ompi/mpi/man/man?/ be full-fledged Makefile.am's (vs. Makefile.extras that are designed to be included in ompi/Makefile.am). It is more convenient to test generation / installation of man pages when you can "make" and "make install" in their respective directories (vs. doing a build / install for the entire ompi project). 4. Removed logic from ompi/Makefile.am that re-generated man pages if opal_config.h changes. Other man pages -- hopefully all of them! -- will be converted to Markdown over time. Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2020-04-20 19:43:59 +03:00
ompi/mpi/man/man3/Makefile
ompi/mpi/man/man5/Makefile
ompi/tools/ompi_info/Makefile
ompi/tools/wrappers/Makefile
ompi/tools/wrappers/mpicc-wrapper-data.txt
ompi/tools/wrappers/mpic++-wrapper-data.txt
ompi/tools/wrappers/mpifort-wrapper-data.txt
ompi/tools/wrappers/ompi.pc
ompi/tools/wrappers/ompi-c.pc
ompi/tools/wrappers/ompi-cxx.pc
ompi/tools/wrappers/ompi-fort.pc
ompi/tools/wrappers/mpijavac.pl
ompi/tools/mpisync/Makefile
ompi/tools/mpirun/Makefile
])
])