4eb3ee7835
We have repeatedly seen users inadvertantly try to use a C compiler for $CXX (e.g., using icc instead of icpc in recent versions of the Intel compiler). Unfortunately, this would "sorta work", meaning that configure would complete successfully and the build would fail much later in the process (when $CXX was used to try to link a C++ compiler). This was further compounded by the fact that many C compilers will switch into "C++ mode" when they compile files that end in .cc -- meaning that they'll *compile* C++ codes properly, but they won't *link* properly. Hence, users would get all the way down to compiling the C++ MPI bindings or ompi_info (i.e., very late in the build process) before the problem became evident. We already have a test in configure that tries to compile, link, and run a sample C++ program. This helped ensure that $CXX was a valid compiler, but it did not catch if the user accidentally supplied a C compiler instead of a C++ compiler because the test program was simply "return 0". This commit updates the test program to use some C++-specific constructs (std::string) so that if the user supplies a C compiler in $CXX, the program may *compile*, but it will definitely fail to *link*. Hence, the process will fail early in configure (with a descriptive message about how the compiler failed to work properly) rather than late in the build. This commit was SVN r10829.
176 строки
5.8 KiB
Bash
176 строки
5.8 KiB
Bash
dnl -*- shell-script -*-
|
|
dnl
|
|
dnl Copyright (c) 2004-2006 The Trustees of Indiana University and Indiana
|
|
dnl University Research and Technology
|
|
dnl Corporation. All rights reserved.
|
|
dnl Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
dnl of Tennessee Research Foundation. All rights
|
|
dnl reserved.
|
|
dnl Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
dnl University of Stuttgart. All rights reserved.
|
|
dnl Copyright (c) 2004-2005 The Regents of the University of California.
|
|
dnl All rights reserved.
|
|
dnl $COPYRIGHT$
|
|
dnl
|
|
dnl Additional copyrights may follow
|
|
dnl
|
|
dnl $HEADER$
|
|
dnl
|
|
dnl OMPI_SETUP_F90
|
|
dnl
|
|
dnl sets:
|
|
dnl F90 : full pathname to compiler
|
|
dnl BASEF90 : compiler name (no path)
|
|
dnl OMPI_WANT_F90_BINDINGS : (actually set by ompi_configure_options, may be
|
|
dnl redefined here)
|
|
dnl FC : Same as F90. Side effect of AC_PROG_FC. Should
|
|
dnl not be used
|
|
dnl defines:
|
|
dnl OMPI_F90 : same as F90
|
|
dnl OMPI_WANT_F90_BINDINGS :
|
|
dnl am_conditional:
|
|
dnl OMPI_WANT_F90_BINDINGS :
|
|
|
|
AC_DEFUN([OMPI_SETUP_F90],[
|
|
|
|
# Modularize this setup so that sub-configure.in scripts can use this
|
|
# same setup code.
|
|
|
|
ompi_show_subtitle "Fortran 90/95 compiler"
|
|
|
|
if test "$OMPI_WANT_F77_BINDINGS" = "0" ; then
|
|
AC_MSG_WARN([*** Fortran 90/95 bindings implicitly disabled (because])
|
|
AC_MSG_WARN([*** Fortran 77 bindings were disabled)])
|
|
|
|
OMPI_WANT_F90_BINDINGS=0
|
|
OMPI_F90="none"
|
|
BASEF90="none"
|
|
OMPI_F90_ABSOLUTE="none"
|
|
if test "$enable_f90" = "yes"; then
|
|
AC_MSG_WARN([*** but --enable-f90 was explicitly specified])
|
|
AC_MSG_ERROR([Cannot continue])
|
|
fi
|
|
elif test "$OMPI_WANT_F90_BINDINGS" = "0" ; then
|
|
AC_MSG_WARN([*** Fortran 90/95 bindings disabled by user])
|
|
OMPI_WANT_F90_BINDINGS=0
|
|
OMPI_F90="none"
|
|
BASEF90="none"
|
|
OMPI_F90_ABSOLUTE="none"
|
|
else
|
|
|
|
#
|
|
# Check for the compiler
|
|
#
|
|
# Note that we don't actually *use* the fortran compiler to build
|
|
# anything in OMPI; it's only used here in configure to find out
|
|
# symbol conventions, type sizes, etc. We also pass it down to
|
|
# the wrapper compiler mpif90.
|
|
#
|
|
# Note that AC_PROG_FC will look for *any* fortran compiler, and
|
|
# we don't want it to find an F77 compiler. The AC docs don't
|
|
# recommend using the "dialect" feature of AC_PROG_FC (and you can
|
|
# only look for one of Fortran 90 or 95 -- not both), so instead
|
|
# use the optional first parameter and steal the list of Fortran
|
|
# compilers (excluding the f77 compiler names) from AC's default
|
|
# list of 95 and 90 compilers and use it here.
|
|
#
|
|
|
|
ompi_fcflags_save="$FCFLAGS"
|
|
AC_PROG_FC([gfortran f95 fort xlf95 ifort ifc efc pgf95 lf95 f90 xlf90 pgf90 epcf90])
|
|
FCFLAGS="$ompi_fcflags_save"
|
|
if test -z "$FC"; then
|
|
AC_MSG_WARN([*** Fortran 90/95 bindings disabled (could not find compiler)])
|
|
OMPI_WANT_F90_BINDINGS=0
|
|
OMPI_F90="none"
|
|
BASEF90="none"
|
|
OMPI_F90_ABSOLUTE="none"
|
|
else
|
|
OMPI_WANT_F90_BINDINGS=1
|
|
OMPI_F90="$FC"
|
|
BASEF90="`basename $FC`"
|
|
OMPI_F90_ABSOLUTE="`which $FC`"
|
|
fi
|
|
fi
|
|
# make sure the compiler actually works, if not cross-compiling
|
|
# Don't just use the AC macro so that we can have a pretty
|
|
# message.
|
|
AS_IF([test $OMPI_WANT_F90_BINDINGS -eq 1],
|
|
[OMPI_CHECK_COMPILER_WORKS([Fortran], [], [], [],
|
|
[AC_MSG_ERROR([Could not run a simple Fortran program. Aborting.])])])
|
|
|
|
# check to see if the F77 and F90 compilers are compatible
|
|
AS_IF([test $OMPI_WANT_F90_BINDINGS -eq 1],
|
|
[AC_MSG_CHECKING([whether $OMPI_F77 and $OMPI_F90 compilers are compatible])
|
|
OMPI_INTL_F90_F77_INTERACTION([fortran_goodness=1], [fortran_goodness=0])
|
|
if test "$fortran_goodness" = "0" ; then
|
|
AC_MSG_RESULT([no])
|
|
AC_MSG_WARN([*** Fortran 77 and Fortran 90 compilers are not link compatible])
|
|
AC_MSG_WARN([*** Disabling MPI Fortran 90/95 bindings])
|
|
OMPI_WANT_F90_BINDINGS=0
|
|
else
|
|
AC_MSG_RESULT([yes])
|
|
fi
|
|
])
|
|
|
|
# if we're still good, then save the extra file types. Do this last
|
|
# because it implies tests that should be invoked by the above tests
|
|
# (e.g., running the fortran compiler).
|
|
AS_IF([test $OMPI_WANT_F90_BINDINGS -eq 1],
|
|
[AC_LANG_PUSH(Fortran)
|
|
AC_FC_SRCEXT(f)
|
|
AC_FC_SRCEXT(f90)
|
|
AC_LANG_POP(Fortran)])
|
|
|
|
# All done -- save values
|
|
AC_DEFINE_UNQUOTED(OMPI_WANT_F90_BINDINGS, $OMPI_WANT_F90_BINDINGS,
|
|
[Whether we want the MPI f90 bindings or not])
|
|
AC_DEFINE_UNQUOTED(OMPI_F90, "$OMPI_F90", [OMPI underlying F90 compiler])
|
|
AM_CONDITIONAL(OMPI_WANT_F90_BINDINGS, test "$OMPI_WANT_F90_BINDINGS" = "1")
|
|
AC_SUBST(OMPI_F90_ABSOLUTE)
|
|
unset fortran_goodness
|
|
])
|
|
|
|
#############################################################################
|
|
|
|
AC_DEFUN([OMPI_INTL_F90_F77_INTERACTION], [
|
|
# make sure that we can combine F90 and F77 code
|
|
AC_LANG_PUSH(Fortran)
|
|
# Fortran module
|
|
cat > conftestf77.f <<EOF
|
|
subroutine Conf1_test()
|
|
end
|
|
EOF
|
|
cat > conftestf90.f <<EOF
|
|
program main
|
|
call Conf1_test()
|
|
end
|
|
EOF
|
|
|
|
# Try the compile
|
|
OMPI_LOG_COMMAND(
|
|
[$OMPI_F90 $FCFLAGS $FCFLAGS_f -c conftestf90.f],
|
|
OMPI_LOG_COMMAND(
|
|
[$OMPI_F77 $FFLAGS -c conftestf77.f],
|
|
OMPI_LOG_COMMAND(
|
|
[$OMPI_F90 $FCFLAGS -o conftest conftestf90.o conftestf77.o $LIBS],
|
|
[HAPPY=1],
|
|
[HAPPY=0]),
|
|
[HAPPY=0]),
|
|
[HAPPY=0])
|
|
|
|
if test "$HAPPY" = "1"; then
|
|
$1
|
|
else
|
|
OMPI_LOG_MSG([here is the F77 program:], 1)
|
|
OMPI_LOG_FILE([conftestf77.f])
|
|
OMPI_LOG_MSG([here is the F90 program:], 1)
|
|
OMPI_LOG_FILE([conftestf90.f])
|
|
$2
|
|
fi
|
|
|
|
unset HAPPY ompi_conftest_h
|
|
/bin/rm -f conftest*
|
|
|
|
AC_LANG_POP(Fortran)
|
|
])dnl
|