The legacy API is has been (internally) ported to use the new interface.
The intent is that users of the legacy API do not have to change their
codes.

Next step is to completely adapt the .gitlab-ci.yml file

It was previously not possible to disable this flag

Still missing is the compatibility layer, currently it only compiles
when configure is called with

  --disable-legacy

Also, a more general solution to parameter passing via environment
variables would be nice.

This reverts commit 64ec6ec2.

There are also at least those files, where stops without 1 are present

src/elpa1/legacy_interface/elpa_cholesky_template_legacy.X90:
src/elpa1/legacy_interface/elpa_invert_trm_legacy.X90:
src/elpa1/legacy_interface/elpa_multiply_a_b_legacy.X90:
src/elpa1/legacy_interface/elpa_solve_tridi_legacy.X90:

should they be also changed?

on misnky

PGI's compiler wants

  -module

as the flag to specify the module output directory. Sadly, this is also
a libtool argument, resulting in much sorrow.

Thus, we have to escape -module by prefixing it with -Xcompiler. Sadly
libtool is not used everywhere by automake, thus we have to remove it
again in those cases were it would be passed to the compiler and cause
sorrow there.

Sad story. But with a happy ending?

Those are now handled in a C header

Sometimes the compiler is used with the manual_cpp wrapper, do not
invoke this for linking

This is used to check if we compile Fortran with PGI or Intel and to
then use the CPP wrapper script.

It would be nice to change this check to test for actual misbehaviour of
the preprocessor. TBD

Two issues: executable was named differently and the CI test names were
colliding

Enough is enough, C99 is not too much to ask in 2017

Supports multiple indexes now, to be used for non-tunable 'parameters'