[mpich-discuss] function declaration conflicts in mpicxx.h
Yang Xin
zincumyx at gmail.com
Wed Jan 27 16:51:18 CST 2010
yes, that's the reason why I can not compile my codes. It has been solved
now, thank you all for the helps!
Regards,
Xin
On Tue, Jan 26, 2010 at 8:30 PM, Justin Luitjens <luitjens at cs.utah.edu>wrote:
> 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
> >
> >
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20100127/9edec6d1/attachment.htm>
More information about the mpich-discuss
mailing list