[mpich-discuss] function declaration conflicts in mpicxx.h

Justin Luitjens luitjens at cs.utah.edu
Tue Jan 26 20:30:43 CST 2010


I saw a similar problem on Kraken, it turned out that I was using a C
compiler instead of a C++ compiler.

Justin

On Mon, Jan 25, 2010 at 12:37 PM, Jeff Squyres <jsquyres at cisco.com> wrote:
> On Jan 25, 2010, at 2:32 PM, Dave Goodell wrote:
>
>> I can't remember off the top of my head if this is required behavior
>> according to the MPI Standard, but it looks like OpenMPI does the same
>> thing.
>
> MPI requires that "mpi.h" work in both C and C++ contexts.
>
> But I can definitely see that
>
> extern "C" {
> #include "mpi.h"
> }
>
> would be problematic if compiled by a C++ compiler.
>
> --
> Jeff Squyres
> jsquyres at cisco.com
>
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>
>


More information about the mpich-discuss mailing list