This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Thanks for your suggestion. I resend my question here.
> 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 1.7's Java implementation under ompi/mpi/java seem to be able to build up independently. Do you think we can build just them and run it (via prunjava?) with our custom OpenMPI build based on 1.6?
On 2013/01/10, at 2:38, Jeff Squyres (jsquyres) <jsquyres_at_[hidden]> wrote:
> 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
> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
> users mailing list
>> The MPI Java binding being developed on the 1.7 pre-release. Is it possible to merge it with 1.5 or 1.6 releases?
>> Our OpenMPI installation has large modifications to adopt specific network channels. Thus, it would be happy to work the MPI Java binding even with old OpenMPI binaries/libraries.
>> Thanks a lot for any comment in advance.