Prepare ELPA 2016.05.002 release

parent d71a1394
Changelog for release ELPA 2016.05.001
- fix problem with generated *.sh- check scripts
- name library differently if build without MPI support
Changelog for release ELPA 2016.05.001 Changelog for release ELPA 2016.05.001
- support building without MPI for one node usage - support building without MPI for one node usage
......
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
## Preamle ## ## Preamle ##
This file provides documentation on how to build the *ELPA* library in **version ELPA-2016.05.001**. This file provides documentation on how to build the *ELPA* library in **version ELPA-2016.05.002**.
Although most of the documentation is generic to any *ELPA* release, some configure options Although most of the documentation is generic to any *ELPA* release, some configure options
described in this document might be specific to the above mentioned version of *ELPA*. described in this document might be specific to the above mentioned version of *ELPA*.
...@@ -110,6 +110,9 @@ by applications, which do not have any MPI parallelisation. To set this version, ...@@ -110,6 +110,9 @@ by applications, which do not have any MPI parallelisation. To set this version,
"--with-mpi=0" configure flag. It is strongly recommmended to also set the "--enable-openmp" "--with-mpi=0" configure flag. It is strongly recommmended to also set the "--enable-openmp"
option, otherwise no parallelisation whatsoever will be present. option, otherwise no parallelisation whatsoever will be present.
It is possible to install the different flavours of ELPA (with/without MPI, with/without OpenMP) in the same
directory, since the library is named differently for each build.
### Doxygen documentation ### ### Doxygen documentation ###
A doxygen documentation can be created with the "--enable-doxygen-doc" configure option A doxygen documentation can be created with the "--enable-doxygen-doc" configure option
......
...@@ -37,6 +37,4 @@ https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html ...@@ -37,6 +37,4 @@ https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
Compatible API change w.r.t. previous version: Interfaces have been added to unify Compatible API change w.r.t. previous version: Interfaces have been added to unify
the naming conventions. The old interface are still available the naming conventions. The old interface are still available
The state of release 2016.05.001 defines this interface The states of release 2016.05.001 and 2016.05.002 define this interface
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
## Current Release ## ## Current Release ##
The current release is ELPA 2016.05.001 The current release is ELPA 2016.05.002
## About *ELPA* ## About *ELPA*
...@@ -87,7 +87,7 @@ the possible configure options. ...@@ -87,7 +87,7 @@ the possible configure options.
## Using *ELPA* ## Using *ELPA*
Please have a look at the "**USERS_GUIDE**" file, to get a documentation or at the [online] Please have a look at the "**USERS_GUIDE**" file, to get a documentation or at the [online]
(http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2016.05.001/html/index.html) doygen (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2016.05.002/html/index.html) doygen
documentation, where you find the definition of the interfaces. documentation, where you find the definition of the interfaces.
## Contributing to *ELPA* ## Contributing to *ELPA*
......
This file contains the release notes for the ELPA 2016.05.001 version This file contains the release notes for the ELPA 2016.05.002 version
What is new? What is new?
------------- -------------
For changes since release ELPA 2015.11.011 please have a loog at the Changelog file For changes since release ELPA 2016.05.001 please have a look at the Changelog file
a) ABI change a) ABI change
--------------------- ---------------------
Most importantly, the ABI of the ELPA library changed! Since release 2016.05.001 the ABI has not changed
New interfaces have been added, the old ones still exists, thus a rebuild
of your code (build with ELPA 2015.11.001) should not be necessary. However,
it is not guaranteed whether your Fortran compiler produces compatible
Fortran modules if content is added to this modules. To be on the safe sight,
re-compiling your application with the new ELPA version is not a bad idea.
For details of the ABI changes (including the history of changes) please have a
look at the "LIBRARY_INTERFACE" file
Any incompatibilities to previous version? Any incompatibilities to previous version?
--------------------------------------- ---------------------------------------
As mentioned before, the ABI of ELPA was changed such, that there should be no As mentioned before, the ABI of ELPA was not changed; There is no
incompatibility with the previous version ELPA 2015.11.001. There is an incompatibility with the previous version ELPA 2016.05.001. and ELPA 2015.11.001 releases. There is, however, an incompatibility with older versions than ELPA 2015.11.001 !
incompatibility with older versions than ELPA 2015.11.001 !
...@@ -9,7 +9,7 @@ Local documentation (via man pages) should be available (if *ELPA* has been inst ...@@ -9,7 +9,7 @@ Local documentation (via man pages) should be available (if *ELPA* has been inst
For example "man get_elpa_communicators" should provide the documentation for the *ELPA* function which sets For example "man get_elpa_communicators" should provide the documentation for the *ELPA* function which sets
the necessary communicators. the necessary communicators.
Also a [online doxygen documentation] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2016.05.001/html/index.html) Also a [online doxygen documentation] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2016.05.002/html/index.html)
for each *ELPA* release is available. for each *ELPA* release is available.
### General concept of the *ELPA* library ### ### General concept of the *ELPA* library ###
...@@ -20,7 +20,7 @@ The *ELPA* library consists of two main parts: ...@@ -20,7 +20,7 @@ The *ELPA* library consists of two main parts:
Both variants of the *ELPA* solvers are available for real or complex valued matrices. Both variants of the *ELPA* solvers are available for real or complex valued matrices.
Thus *ELPA* provides the following user functions (see man pages or [online] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2016.05.001/html/index.html) for details): Thus *ELPA* provides the following user functions (see man pages or [online] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2016.05.002/html/index.html) for details):
- get_elpa_communicators : set the row / column communicators for *ELPA* - get_elpa_communicators : set the row / column communicators for *ELPA*
- solve_evp_complex_1stage : solve a complex valued eigenvale proplem with the *ELPA 1stage* solver - solve_evp_complex_1stage : solve a complex valued eigenvale proplem with the *ELPA 1stage* solver
......
AC_PREREQ([2.69]) AC_PREREQ([2.69])
# Remember to change the version also in elpa.spec # Remember to change the version also in elpa.spec
AC_INIT([elpa],[2016.05.001], [elpa-library@mpcdf.mpg.de]) AC_INIT([elpa],[2016.05.002], [elpa-library@mpcdf.mpg.de])
AC_SUBST([PACKAGE_VERSION]) AC_SUBST([PACKAGE_VERSION])
...@@ -34,7 +34,7 @@ AM_SILENT_RULES([yes]) ...@@ -34,7 +34,7 @@ AM_SILENT_RULES([yes])
# by the current interface, as they are ABI compatible (e.g. only new symbols # by the current interface, as they are ABI compatible (e.g. only new symbols
# were added by the new interface) # were added by the new interface)
# #
AC_SUBST([ELPA_SO_VERSION], [5:0:1]) AC_SUBST([ELPA_SO_VERSION], [5:1:1])
# #
......
AC_PREREQ([2.69]) AC_PREREQ([2.69])
AC_INIT([elpa_test_project],[2016.05.001], elpa-library@rzg.mpg.de) AC_INIT([elpa_test_project],[2016.05.002], elpa-library@rzg.mpg.de)
elpaversion="2016.05.001" elpaversion="2016.05.002"
AC_CONFIG_SRCDIR([src/test_real.F90]) AC_CONFIG_SRCDIR([src/test_real.F90])
AM_INIT_AUTOMAKE([foreign -Wall subdir-objects]) AM_INIT_AUTOMAKE([foreign -Wall subdir-objects])
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment