Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] MPIT solution still wrong
From: Ralph Castain (rhc_at_[hidden])
Date: 2013-08-19 22:21:30

Agreed - I was simply trying to get it to build because it broke some developers here.

On Aug 19, 2013, at 6:03 PM, "Jeff Squyres (jsquyres)" <jsquyres_at_[hidden]> wrote:

> It looks like is a stopgap, but it is still definitely wrong.
> The MPIT stuff does *not* compile the same way the C bindings compile. Here's how the C bindings compile:
> a) in ompi/mpi/c/profile: always compile
> b) in ompi/mpi/c:
> 1. always compile (a small number of stub functions and global variables)
> 2. only compile if weak symbols are not supported (e.g., OSX)
> Then always contains a) and b1). If b2) exists, it is also slurped into
> MPIT is currently compiled as:
> a) in ompi/mpi/tool/profile: always compile
> b) in ompi/mpi/tool: always compile
> It really needs to be done the same way the C bindings are done -- split b) into the global constants that you always need and always compile that, and then optionally compile the rest if weak symbols are not supported.
> --
> Jeff Squyres
> jsquyres_at_[hidden]
> For corporate legal information go to:
> _______________________________________________
> devel mailing list
> devel_at_[hidden]