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

Apparently in some compiler/MPI combinations (gcc with impi 5.1.3) the
identifier 'mpi_status' is defined and exporeted in their MPI fortran
module and it is thus not allowed to name one of your local variables
also 'mpi_status'.

The confusing error message I got was

  ../src/elpa2_compute.F90:5780:37:

                  call mpi_wait(ireq_hv,mpi_status,mpierr)
                                       1
  Error: Invalid procedure argument at (1)

even though everything seemed to be defined correctly

Some people had problems finding the ELPA email address, thus
is is clearly specified here

The subroutine solve_tridi has NOT been shifted from the private
module "elpa1_compute" to the public module elpa1_auxilliary.

Instead, a wrapper function solve_tride has been introduced, which
calls (via Fortran module association) the private function.

This does what it is supposed to do, but should be cleaned up at
some time. Public functions (interfaces) should be implemented in
a public module

These functions were made private with ELPA releases 2016.05.001
and 2016.05.002, but they should be public

Now they just cluttered the main build directory, put them also in
private_modules/. This of course assumes that no two test programs
define modules with the same name.

Also, this necessitates that the shared sources are also only compiled
once, thus I put them into an internal libtool convenience library and
link all test programs with it.

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