From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Fwd: Re: [OMPI users] libmpi_f90 shared lib version number change in 1.6.3
Date: Fri, 18 Jan 2013 12:07:00 -0000 [thread overview]
Message-ID: <50F93B06.1010809@gmail.com> (raw)
In-Reply-To: <EF66BBEB19BADC41AC8CCF5F684F07FC380BC298@xmb-rcd-x01.cisco.com>
Hi,
what is the preferred way to recover the situation
of this upstream incident ?
currently we have on 1.6.3:
libopenmpif90_3 usr/bin/cygmpi_f90-3.dll
if I follow upstream on next 1.6.4
libopenmpif90_1 usr/bin/cygmpi_f90-1.dll
Currently no package depends on libopenmpif90_3
Regards
Marco
-------- Original Message --------
Subject: Re: [OMPI users] libmpi_f90 shared lib version number change in
1.6.3
Date: Wed, 16 Jan 2013 17:12:09 +0000
From: Jeff Squyres
Reply-To: Open MPI Users
To: Open MPI Users
On Jan 12, 2013, at 5:06 AM, Ake Sandgren wrote:
> Was the change for libmpi_f90 in VERSION intentional or a typo?
> This is from openmpi 1.6.3
> libmpi_f90_so_version=4:0:1
> 1.6.1 had
> libmpi_f90_so_version=2:0:1
It was both intentional and a typo.
Specifically, it really should have bee 4:0:3. :-(
Meaning: we unintentionally broke the F90 ABI for 1.6.3 (specifically:
OMPI applications compiled to utilize "use mpi"). :-( :-( :-(
This ABI compatibility will be restored in 1.6.4.
-----
See these commit messages for a fuller explanation:
https://svn.open-mpi.org/trac/ompi/changeset/27471
https://svn.open-mpi.org/trac/ompi/changeset/27558
The short explanation is that, in terms of the "use mpi" interface, all
Open MPI 1.6.x versions are ABI compatible except 1.6.3.
These work:
- compile a "use mpi" OMPI application with 1.6.x (where x!=3), change
your LD_LIBRARY_PATH to point to a different OMPI 1.6.x installation
(where x!=3)
- compile a "use mpi" OMPI application with 1.6.3, use it with OMPI
1.6.3 installation
These do not:
- compile a "use mpi" OMPI application with 1.6.x (where x!=3), change
your LD_LIBRARY_PATH to point an OMPI 1.6.3 installation
- compile a "use mpi" OMPI application with 1.6.3, use it with OMPI
1.6.x installation (where x!=3)
I will make an FAQ item about this so that the result is google-able.
--
Jeff Squyres
jsquyres@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________
users mailing list
users@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
next parent reply other threads:[~2013-01-18 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EF66BBEB19BADC41AC8CCF5F684F07FC380BC298@xmb-rcd-x01.cisco.com>
2013-01-18 12:07 ` marco atzeri [this message]
2013-01-23 11:41 ` Yaakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50F93B06.1010809@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).