These are saved in the .log files by the test-driver anyway and do not
clutter the screen output for the user. But having them can be useful to
find out how some test failed.

- the ascii files "INSTALL", "README", and "RELEASE_NOTES" are
  updated
- the Makefile.example in the test directory is updated

The fdep magic only works within a single Automake target, add the
remaining dependencies by hand. Parallel compilation should now work
also for "make all" again.

Since the tar-balls are availabel on the ELPA website
, http://elpa.rzg.mpg.de/ , this directory is not useful anymore
and just wastes disk space

libtool was too smart and mixed Intel and GNU OpenMP libraries

The Intel MPI g++ compiler wrapper otherwise links with the
non-threadsafe mpi libary instead of mpi_mt, leading to link errors.

config-f90.h should not be delete by make clean, as it is created by
configure, not by the build processes.
Also, better keep the directories modules/ and .fortran_dependencies/
and only delete their contents.

A special marker in the assembler file for the SSE kernel is needed to
allow to declare the stack non-executable, which was criticized by
the packaging tools of the openSUSE build service.

The library will thus be called libelpa-2014.06.so

Rename all binaries to have an elpa1_, or elpa2_ prefix.
Additionally, also ship a README and license file.

With this, the pkg-config installation can be verified

This includes a number of changes:

- ScaLAPACK2 on from the openSUSE:science repository is now correctly
  auto-detected. As ScaLAPACK2 already includes BLACS, an additional
  BLACS library must not be linked!

- The resulting library is now called elpa-2014.06.000.so, as was
  probably originally intended anyway

- The pkg-config file was renamed to elpa-2014.06.000.pc and filled with
  correct values. With this, a package using ELPA can easily get the
  necessary compilation and library flags.

In this commit, only the "precious" files (Makefile.am, configure.ac,
etc.) are included, to make clear what has been changed by hand.

In the subsequent commit also all autoconf generated files will follow.

Without this, automake tries to be smart and rebuilt the autoconf
generated files such as configure, aclocal.m4, etc., in case the
timestamps of files such as configure.ac are newer.

This only makes trouble for end users with out-of-date autoconf versions
that cannot produce these files.

If one species a kernel with the "--with-kernel-name" option,
this means that only this (real/complex) is configured and
installed. All other available real/complex kernels are not considered.

Thus the help messages (see ./configure --help) is changed
such that the option is called

"--with-only-kernel-name"

- the library version number is changed due to change in ABI
- the INSTALL ascii file is updated
- a RELEASE_NOTES file is introduced