I reviewed the v1.8 logs and I think that this is what the shared library version numbers should be. Essentially: most have minor code changes, meaning that they should get an revision bump (the "r" in c:r:a). And the rest should get also get a revision bump because mutex.h changed. This latter part might be a little overkill, but I think it's harmless (and I don't feel like checking closely to see if mutex.h directly affects each shared library that didn't have other code changes).
Can someone please double check these? ----- # JMS Multiple changes in OMPI code: was 7:0:6 libmpi_so_version=7:1:6 libmpi_cxx_so_version=2:3:1 # JMS Fortran code changed: was 7:0:5 libmpi_mpifh_so_version=7:1:5 # JMS Fortran code changed: was 5:0:4 libmpi_usempi_tkr_so_version=5:1:4 # JMS Fortran code changed: was 1:0:1 libmpi_usempi_ignore_tkr_so_version=1:1:1 # JMS Fortran code changed: was 6:0:6 libmpi_usempif08_so_version=6:1:6 # JMS ORTE code changed: was 7:5:0 libopen_rte_so_version=7:6:0 # JMS Multiple changes in OPAL code: was 8:1:2 libopen_pal_so_version=8:2:2 libmpi_java_so_version=3:0:2 # JMS Oshmem code changed: was 3:1:0 liboshmem_so_version=3:2:0 # OMPI layer # JMS cuda code changed: was 1:7:0 libmca_common_cuda_so_version=1:8:0 # JMS Changed opal/thread/mutex.h: was 2:5:0 libmca_common_mx_so_version=2:6:0 # JMS Changed opal/thread/mutex.h: was 4:4:0 libmca_common_sm_so_version=4:5:0 # JMS Changed opal/thread/mutex.h: was 2:1:2 libmca_common_ugni_so_version=2:2:2 # JMS Changed opal/thread/mutex.h: was 2:3:2 libmca_common_verbs_so_version=2:4:2 # OPAL layer # JMS Changed opal/thread/mutex.h: was 2:3:1 libmca_opal_common_pmi_so_version=2:4:1 ----- -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
