ab398f4b9a
Automake's Fortran compilation rules inexplicably use CPPFLAGS and AM_CPPFLAGS. Unfortunately, this can cause problems in some cases (e.g., picking up already-installed mpi.mod in a system-default include search path). So in relevant module-using Fortran compilation Makefile.am's, zero out CPPFLAGS and AM_CPPFLAGS. This has a side-effect of requiring that we compile the one .c file in the F08 library in a new, separate subdirectory (with its own Makefile.am that does _not_ have CPPFLAGS/AM_CPPFLAGS zeroed out). Signed-off-by: Jeff Squyres <jsquyres@cisco.com> Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
35 строки
957 B
Makefile
35 строки
957 B
Makefile
# -*- makefile -*-
|
|
#
|
|
# Copyright (c) 2019 Cisco Systems, Inc. All rights reserved.
|
|
#
|
|
# $COPYRIGHT$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
|
|
include $(top_srcdir)/Makefile.ompi-rules
|
|
|
|
# This Makefile is only relevant if we're building the "use mpi_f08"
|
|
# MPI bindings.
|
|
if OMPI_BUILD_FORTRAN_USEMPIF08_BINDINGS
|
|
|
|
# This directory only exists so that we can separate C compilation
|
|
# from Fortran compilation. Specifically: note that Automake's
|
|
# Fortran-buidling rules uses CPPFLAGS and AM_CPPFLAGS. This can
|
|
# cause weirdness (e.g.,
|
|
# https://github.com/open-mpi/ompi/issues/7253). So when compiling
|
|
# Fortran, we should zero out CPPFLAGS and AM_CPPFLAGS.
|
|
|
|
# HOWEVER, we have one .c file in the use-mpi-f08 library. So we have
|
|
# to split it out to its own directory / Makefile.am where CPPFLAGS /
|
|
# AM_CPPFLAGS are *not* zeroed out.
|
|
|
|
noinst_LTLIBRARIES = libusempif08_ccode.la
|
|
|
|
libusempif08_ccode_la_SOURCES = \
|
|
buffer_detach.c
|
|
|
|
endif
|