[bugfix] Produce a linker error when pardiso lib is not found

If somebody tries to use pardiso despite it not being found,
he should ge t a linker error instead of an exception.
All other bindings handle it that way.

Fixes flyspray/FS#351

See merge request !4

[cleanup] Use template aliases where they beautify code.

I already wanted to use those when implementing the UMFPack
integration into the overlapping schwarz, but our compiler
requirements were not sufficient at the time.

See merge request !9

I already wanted to use those when implementing the UMFPack
integration into the overlapping schwarz, but our compiler
requirements were not sufficient at the time.

Feature/fix deprecation warnings amgtest

please see flyspray/FS#1526

@markus.blatt can you have a look (somehow I can't assign this request to you)

See merge request !7

Apparently, this has been rotting away for quite some time. Adapt the
calls to the Pardiso library. Use the C instead of the Fortran interface.
Use correct method for determining the block size of the matrix.

Fixup for !2

Bug introduced in the fix of flyspray/FS#1331 and !2
revealed by simply building dune-istl.

See merge request !6

Bug introduced in the fix of flyspray/FS#1331 and !2
revealed my `make build_tests`.

[real_type] use real_type for all norm computations, fix flyspray/FS#1331

I think these are the last places where double has to be replaced. The only remaining places are superlu and umfpack which are not templated and thus are hardcoded to use double.

This patch fixes flyspray/FS#1331

See merge request !2

Some exceptions were caught and did not fail the test.

needed for webpage.

If somebody tries to use pardiso despite it not being found,
he should ge t a linker error instead of an exception.
All other bindings handle it that way.

Fixed flyspray/FS#351

Feature/fs1659 matlab output of dynamic matrix

fixed flyspray/FS#1659

See merge request !3

This enables users to have several build directories like
build-clang, build-gcc5, build-debug, and still get all
of them ignored.

There are some tests, which are hard to port in the paamg directory.
They want to explicitly test _without_ direct solver. Previously,
you simply did not add the flags for the direct solver packages.
add_dune_test relies on all flags, so we need a way to disable components
again. That will be implemented as part of dune_add_executable. For
now, we build the targets ourselves and hand them to dune_add_test.

This enables users to have several build directories like
build-clang, build-gcc5, build-debug, and still get all
of them ignored.

This partially fixes FS#1724.

Similar to commit e8d16384 which
added the same for UMFPack.
This avoids strange bugs when using the setSubMatrix method: that method
automatically removes rows and columns from the matrix, and expects
_the user_ to do the same for the x and b vectors.

Let FindPackageHandleStandardArgs handle missing dependencies.
Mark ARPACKPP_LIBRARY as advanced.
Remove dead code.

It's confusing and against our style-guide.

The arpack++ package from Debian comes with a shared library that we
have to link to. Otherwise the linker will complain about missing
symbols when we try to build arpackpptest.
As there seem to be other versions of arpack++ that are header-only, we
only link to the shared library if it was found.

There are some tests, which are hard to port in the paamg directory.
They want to explicitly test _without_ direct solver. Previously,
you simply did not add the flags for the direct solver packages.
add_dune_test relies on all flags, so we need a way to disable components
again. That will be implemented as part of dune_add_executable. For
now, we build the targets ourselves and hand them to dune_add_test.

These header are no longer used.

The commit broke compiling / linking if one package was found but
the includes / libraries were not added. We need a different
approach to hide the ENABLE_* trick from the user and keep full
testing capabilities.
This reverts commit 27613560.

This avoids strange bugs when using the setSubMatrix method: that method
automatically removes rows and columns from the matrix, and expects _the user_
to do the same for the x and b vectors.