I would like some opinions on the situation
with the openmpi 1.1 vs 1.2 release series. The
current stable release of openmpi is now 1.2.2.
The libmpi.0.dylib, libmpi_cxx.0.dylib and
libmpi_f77.0.dylib libraries have the same
compatibility numbers (1.0.0) as the 1.1.5
release. However the openmpi developers have
renamed the libopal.0.0.0.dylib and the
liborte.0.0.0.dylib share libraries as
libopen-pal.0.dylib and libopen-rte.0.dylib.
It appears that the release is supposed
to be backwardly compatible even with this
change as long as the packages using openmpi
use the provided compiler tools to build.
Could everyone check if their packages
using openmpi explicitly links in
libopal or liborte into their programs
or libraries? I assume as long as these
were indirectly pulled in from the
other openmpi libraries instead that
we will be okay. I would really like to
avoid creating another forked openmpi
package despite the fact this this violates
the fink rule of changing the names of
distributed libraries. Thanks in advance
for any advice.
Jack
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
