File: VERSION

package info (click to toggle)
openmpi 3.1.3-11
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 118,572 kB
  • sloc: ansic: 628,972; f90: 17,993; makefile: 13,761; sh: 7,051; java: 6,360; perl: 3,215; cpp: 2,225; python: 1,350; lex: 988; fortran: 52; tcl: 12
file content (116 lines) | stat: -rw-r--r-- 4,629 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
# Copyright (c) 2008      Sun Microsystems, Inc.  All rights reserved.
# Copyright (c) 2008-2011 Cisco Systems, Inc.  All rights reserved.
# Copyright (c) 2011      NVIDIA Corporation.  All rights reserved.
# Copyright (c) 2013      Mellanox Technologies, Inc.
#                         All rights reserved.
# Copyright (c) 2016      IBM Corporation.  All rights reserved.
# Copyright (c) 2017      Los Alamos National Security, LLC.  All rights
#                         reserved.

# This is the VERSION file for Open MPI, describing the precise
# version of Open MPI in this distribution.  The various components of
# the version number below are combined to form a single version
# number string.

# major, minor, and release are generally combined in the form
# <major>.<minor>.<release>.

major=3
minor=1
release=3

# greek is generally used for alpha or beta release tags.  If it is
# non-empty, it will be appended to the version number.  It does not
# have to be numeric.  Common examples include: a1 (alpha release 1),
# b1 (beta release 1), rc2 (release candidate 2).  The only
# requirement is that it must be entirely printable ASCII characters
# and have no white space.

greek=

# If repo_rev is empty, then the repository version number will be
# obtained during "make dist" via the "git describe --tags --always"
# command, or with the date (if "git describe" fails) in the form of
# "date<date>".

repo_rev=v3.1.3

# If tarball_version is not empty, it is used as the version string in
# the tarball filename, regardless of all other versions listed in
# this file.  For example, if tarball_version is empty, the tarball
# filename will be of the form
# openmpi-<major>.<minor>.<release><greek>.tar.*.  However, if
# tarball_version is not empty, the tarball filename will be of the
# form openmpi-<tarball_version>.tar.*.

tarball_version=

# The date when this release was created

date="Oct 29, 2018"

# The shared library version of each of Open MPI's public libraries.
# These versions are maintained in accordance with the "Library
# Interface Versions" chapter from the GNU Libtool documentation.  The
# first Open MPI release to programatically specify these versions was
# v1.3.4 (note that Libtool defaulted all prior releases to 0:0:0).
# All changes in these version numbers are dictated by the Open MPI
# release managers (not individual developers).  Notes:

# 1. Since these version numbers are associated with *releases*, the
# version numbers maintained on the Open MPI SVN trunk (and developer
# branches) is always 0:0:0 for all libraries.

# 2. The version number of libmpi refers to the public MPI interfaces.
# It does not refer to any internal interfaces.

# 3. Similar to libmpi, the version numbers of the Fortran libraries
# refer to the public MPI interfaces.  For example, that there have
# been typo fixes in the parameter types to mpif.h Fortran library
# functions over time; these technically did not change the interface
# because Fortran 77 does not link by parameter type.

# 4. Similar to libmpi, libmpi_cxx's version number refers to the
# public MPI interfaces.  Note that this version number may or may not
# be affected by changes to inlined functions in OMPI's
# header-file-based C++ bindings implementation.

# 5. The ORTE and OPAL libraries will change versions when their
# public interfaces change (as relative to the layer(s) above them).
# None of the ORTE and OPAL interfaces are public to MPI applications,
# but they are "public" within the OMPI code base and select 3rd party
# software packages.

# Version numbers are described in the Libtool current:revision:age
# format.

libmpi_so_version=50:3:10
libmpi_cxx_so_version=50:0:10
libmpi_mpifh_so_version=51:2:11
libmpi_usempi_tkr_so_version=50:1:10
libmpi_usempi_ignore_tkr_so_version=50:1:10
libmpi_usempif08_so_version=50:2:10
libopen_rte_so_version=50:3:10
libopen_pal_so_version=50:3:10
libmpi_java_so_version=50:0:10
liboshmem_so_version=50:1:10
libompitrace_so_version=50:0:10

# "Common" components install standalone libraries that are run-time
# linked by one or more components.  So they need to be versioned as
# well.  Yuck; this somewhat breaks the
# components-don't-affect-the-build-system abstraction.

# OMPI layer
libmca_ompi_common_ompio_so_version=50:0:9
libmca_ompi_common_monitoring_so_version=50:0:0

# ORTE layer
libmca_orte_common_alps_so_version=50:0:10

# OPAL layer
libmca_opal_common_cuda_so_version=50:0:10
libmca_opal_common_ofi_so_version=50:0:10
libmca_opal_common_sm_so_version=50:0:10
libmca_opal_common_ugni_so_version=50:0:10
libmca_opal_common_verbs_so_version=50:0:10