- 27 May, 2014 1 commit
-
-
Andreas Marek authored
- the library version number is changed due to change in ABI - the INSTALL ascii file is updated - a RELEASE_NOTES file is introduced
-
- 26 May, 2014 3 commits
-
-
Andreas Marek authored
Now it is possible - to choose the kernel (real and complex independently) at run-time via environment variables, or - to specify the kernel (real and complex independently) at runtime via specifing the kernel in the call to ELPA This has a few implications 1) The ELPA 2014.06 release has a change in the API and is thus not binary compatible with previous versions 2) if no kernels are specified, a default kernel is choosen 3) if a wrong kernel is specified, a default kernel is choosen For sake of simplicity it is still possible to build ELPA with support for only one kernel, as in previous versions. However, it is still not binary compatible to previous versions
-
Andreas Marek authored
Configure checks whether the Fortran environment module is available. If yes, the library is build such, that all messages (from within the library) are printed at the correct stderr unit. If not, then the stderr unit is set to unit=6
-
Andreas Marek authored
The configure.ac of ELPA_2013.11 is cleaned up a bit Also, ELPA_2013.11 is copied to ELPA_2014.06 in order to have the base for the next ELPA release
-