Refs trac:3248

Absoft has determined exactly what the problem is (private members in
derived data typed when compiled with -g), but does not yet have a
timeline for fixing it.

Add a temporary override for Absoft until they are able to fix their
compiler.  This switch will at least allow us to MTT test the rest of
the mpi_f08 functionality with Absoft.

This commit was SVN r27184.

The following Trac tickets were found above:
  Ticket 3248 --> https://svn.open-mpi.org/trac/ompi/ticket/3248

ompi/config/fortran_check_private.m4

@@ -27,6 +27,12 @@ dnl
 AC_DEFUN([OMPI_FORTRAN_CHECK_PRIVATE],[
     AS_VAR_PUSHDEF([private_var], [ompi_cv_fortran_private])
 
+# JMS Temporary override for the Absoft compiler until they are able
+# to fix derived types with private members and -g.
+    AC_ARG_ENABLE([f08-private-status],
+        [AC_HELP_STRING([--disable-f08-private-status],
+            [disable the "private" attribute in the mpi_f08 MPI_Status type for buggy compilers])])
+
     AC_CACHE_CHECK([if Fortran compiler supports private], private_var,
        [AC_LANG_PUSH([Fortran])
         AC_COMPILE_IFELSE([AC_LANG_SOURCE([[module test_for_private
@@ -40,6 +46,11 @@ end module test_for_private]])],
         touch conftest_foo.mod
         rm -rf *.mod 2>/dev/null
         AC_LANG_POP([Fortran])
+
+# JMS Temporary override for the Absoft compiler until they are able
+# to fix derived types with private members and -g.
+        AS_IF([test "enable_f08_private_status" = "no"],
+              [AS_VAR_SET(private_var, no)])
        ])
 
     AS_VAR_IF(private_var, [yes], [$1], [$2])