Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] Backward Compatibility of MPI Java Binding
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2013-01-09 12:38:19


On Jan 8, 2013, at 3:23 AM, Yoshiki SATO <yoshiki_at_[hidden]> wrote:

> Could you let me know the details of that?

We don't have a technical writeup of what changed in the configure/build system between the two; it's just something that happened over time (our methodology is that we branch away from the main development trunk and then only selectively apply patches from the main trunk to the release branch over time).

The differences between the configure/build system between v1.6 and the SVN trunk are now fairly large, for example:

- trunk uses autogen.pl; v1.6 uses autogen.sh
- trunk uses many more <project>_ prefixes (but not all) to m4 macros; v1.6 doesn't
- trunk has most .m4 files in config/; v1.6 distributes them around config/ and <project>/config/ directories
- trunk has different requirements for each
- many global shell variable names have changed between trunk and v1.6
- Fortran support, for example, was completely revamped on the trunk, and has very, very different .m4 tests than v1.6

I think the subsystems you'll have to update to port the Java interface to the v1.6 branch include (this is more-or-less off the top of my head; it is likely not all-inclusive):

- update configure.ac
- port ompi_setup_java.m4 and orte_setup_java.m4
- port ompi/mpi/java
- update ompi/Makefile.am

If you endeavor to do this and need some help, please ask questions over on the devel list (not the user's list).

-- 
Jeff Squyres
jsquyres_at_[hidden]
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/