I looked at that, too -- I think the only reason to have 2 files is that mpi_portable_platform.h is included by mpi.h (its used for knowing how to define __mpi_interface_deprecated__ in mpi.h), and is therefore installed. opal_portable_platform.h is not installed.
On Nov 6, 2013, at 6:40 AM, "Barrett, Brian W" <bwba...@sandia.gov> wrote: > All - > > Is there a reason we have both opal/include/opal_portable_platform.h and > ompi/include/mpi_portable_platform.h? If they're always supposed to have > the same content (which appears to be the case), then it seems like > building mpi_portable_platform.h from opal_portable_platform.h at build > time is a more appropriate path forward. I'll do the work, but wanted > someone else to verify that I wasn't missing something. > > Brian > > -- > Brian W. Barrett > Scalable System Software Group > Sandia National Laboratories > > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
