Eliminate warnings in CI build coming from mpi.h with GCC 4.9.3 and OpenMPI from 1.6.5
Created by: bartlettroscoe
Next Action Status:
Adding -isystem for OpenMPI 1.6. include dir makes warnings go away locally but not for CTest -S script. Asked SEMS if they could patch mpi.h file (but unknown when that might happen). Next: Switch CI build to GCC 4.8.4 which does not emit the warnings?
CC: @trilinos/framework
Description:
With the upgrade to GCC 4.9.3 (see #1002 (closed)), we are now getting a lot of warnings from OpenMPI 1.6.5 headers like:
In file included from /projects/sems/install/rhel6-x86_64/sems/compiler/gcc/4.9.3/openmpi/1.6.5/include/mpi.h:253:0,
from /scratch/rabartl/Trilinos.base/SEMSCIBuild/Trilinos/packages/teuchos/core/src/Teuchos_Time.hpp:56,
from /scratch/rabartl/Trilinos.base/SEMSCIBuild/Trilinos/packages/teuchos/core/src/Teuchos_Time.cpp:45:
/projects/sems/install/rhel6-x86_64/sems/compiler/gcc/4.9.3/openmpi/1.6.5/include/mpi_portable_platform.h:374:34: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
_STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
^
/projects/sems/install/rhel6-x86_64/sems/compiler/gcc/4.9.3/openmpi/1.6.5/include/mpi_portable_platform.h:374:63: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
_STRINGIFY(__GNUC__)"."_STRINGIFY(__GNUC_MINOR__)"."_STRINGIFY(__GNUC_PATCHLEVEL__)
^such as you see, for example, in this CI iteration:
Looking at the new "Clean" build Linux-gcc-4.9.3-MPI_Release_gcc_4.9.3_openmpi_1.8.7_DEV targeted for SIERRA, for example, at:
perhaps our CI build should be upgraded to OpenMPI 1.8.7?
In any case, this story is to make these warnings go away so they don't spam Trilinos developers and CDash.