GitLab

- the version number has been updated
- a warning that this is a pre-release has been added to the configure
  script
- the changelog has been updated
- the test_project versioning is consistent with the ELPA versioning

Conflicts:
	src/elpa1_solve_tridi_real_template.X90

configure can now distinguish the options --enable-assumed-size and
--disable-assumed-size

This can be switched off via --disable-assumed-size

configure can now distinguish the options --enable-assumed-size and
--disable-assumed-size

This can be switched off via --disable-assumed-size

Sometimes it might be desirable that only one of the specifc AVX
kernels (AVX, AVX2, and in the future AVX512) are build, even though the processor
supports all (or several) of these instructions.

The flag --disable-[avx | avx2 | avx512] allows to define which kernels
should NOT be build. The default is: what can be build will be build

The actual reason for the linker problems was that the Fortran libraries
where listed before the object files, by modifying the _LINK automake
variables. The proper way to do is of course to add the necessary
libraries after the object files by appending them to the _LDADD
variables.

As the MPI module was not responsible for the linker problems it is now
used by default, unless explicitly switched off with

  --disable-mpi-module

Also, the C test programs that had these linker errors where previously
not compiled in the OpenMP case, for no obvious reason. Now they are
also included there.

For some strange reason this causes linker errors on _some_
openSUSE_Tumbleweed installations..

It is now

  --enable-timing
  --enable-redirect
  --with-papi

instead of the more confusing

  --with-ftimings
  --with-redirect
  --disable-papi

For once, the --with versions of timing and redirect could not cope with
--with-timing=no, --with-redirect=no (this was interpreted like =yes).
Also, --with switches are supposed to be for optional dependencies on
other software, not for configuring optional parts of the software
itself.

This makes elpa.spec the single point of reference for the version
number, otherwise care would have to been taken to set it in both places

Recent autoconf has complained about the lack of this

A small missing '$' caused a lot of mischief. Augmented also the tests
to detect something like this in the future

Remove all references to private functions and symbols from the public
Fortran modules. Install also only the public modules

This allows to install several versions of the library in the same
directory

If compiled with MPI, the necessary "mpiexec -n 2" was not written
in the check scripts. This commit is based on a patch provided by
Michael Banck from debian.org

The optional build via "--enable-assumed-size-arrays" is also
tested in the CI

Using Fortran assumed size arrays makes debugging a lot harder,
thus as default these are not used in ELPA.
However, it might be, that some compilers make unwanted copies
if calling subroutines with array slices. Then switching back
to assumed size arrays might create a performance gain

Remove all references to private functions and symbols from the public
Fortran modules. Install also only the public modules