As decided in the doodle for FS#1395, really old MPI versions will be
deprecated in the 2.3 release.

This patch adds an additional check to the MPI tests for autotools and
cmake that makes sure the user has an MPI which is at least compliant
with MPI-2.1. If the user's version is older, a warning is generated.

The test uses version macros instead of the more standard runtime
MPI version query interface to avoid problems when cross-compiling.

The check for constexpr was not copied into the distribution.
Unfortunately, the autotools will only warn about a missing macro, but
give valid results otherwise. This patch adds the cxx11_constexpr.m4 to
Makefile.am, so that it is distributed on "make dist".

With this patch dunecontrol will work even if the path to the module
contains spaces. Unfortunately, the tests for dune modules will still
not work as I could not figure out how to use quoting in the CPP_FLAGS.

Previously a non existent file name (umfpack) was used in
Makefile.am. This broke the build with the message:

make[2]: *** Keine Regel vorhanden, um das Target »umfpack«,
  benötigt von »all-am«, zu erstellen.  Schluss.
make[2]: Leaving directory `/home/mblatt/src/dune/current/dune-common/build-auto/m4'

This patch fixes this by using the correct name.

This patch adds test for both CMake and autotools as the
build system.
UMFPack is used by several dune modules (e.g. fem and istl)
the only common required module by both is common. Therefore
we add the test here to make it usable for all modules.

BTW: These tests are taken from Dominics branch of dune-istl.
     Therefore he deserves the credit for them.

we are now checking for different locations of parmetis.h. This makes it possible us the
scotch parmetis implementation (see FS#1370).

we now check for METIS_PartGraphKway, which a symbol we are actually using and which
is in the implementation of scotch (see FS#1370)

As decided on the developer meeting in Aachen, we support (but do not
rely on) the C++11 keyword constexpr. This patch adds an m4-check for
constexpr and a header (cxx11.hh) defining a macro DUNE_CONSTEXPR either
as constexpr or empty (depending on the compiler support for it). It is
then used in FieldVector and FieldMatrix on size, rows, and cols.

If not found, our own fallback implementation will be used.

MPICH has stepped up its versioning scheme, jumping from MPICH2 1.x
to MPICH 3.x, but has stayed compatible to the older MPICH2 versions.
Unfortunately, the macro MPICH2_VERSION used by mpi_config.m4 to detect
the package has been renamed to MPICH_VERSION.

This patch fixes the problem by adding a separate test for MPICH_VERSION
ana making sure that the macro starts with the letter "3".

Some modules do test for complicated symbols,
eg. "&StandardMerge<double,1,1,1>::build;", which lead to broken
configure scripts. In the above case :
" 1>build;
  ;"
as a shell command.
This patch quotes the program body used for AC_LANG_PROGRAM correctly
to prevent this.

The behavior of DebugAllocator depends on whether the compiler supports
rvalue references, so make sure to run the corresponding test.

[[Imported from SVN: r7472]]

templates.

This way dune-common compiles as before if variadic templates _and_
move semantics are not present.

[[Imported from SVN: r7454]]

variadic templates if available. 

This breaks building of the test of debug allocator as it uses std::forward.

[[Imported from SVN: r7453]]

no side effects.

[[Imported from SVN: r7451]]

[[Imported from SVN: r7446]]

[[Imported from SVN: r7434]]

make sure that flags passed with DUNE_LDFLAGS are the first flags in linker test and not duplicated another time.

Fixes flyspray #1270

[[Imported from SVN: r7433]]

[[Imported from SVN: r7429]]

[[Imported from SVN: r7428]]

[Merge][Bugfix] r7422 from branches/release-cmake-2.2: Prevent definition of HAVE_BOOST without value due to race conditions i
n some autoconf versions.

For some autoconf versions there was a race condition between ax_boost_base.m4 a
nd dune_boost_base.m4 resulting in HAVE_BOOST being defined with no value (inste
ad of ENABLE_BOOST). For others there were even two definitions of it (one with 
and one without value). 

This patch renames the symbol being defined in dune_boost_base.m4 to HAVE_DUNE_B
OOST and defines a value for it if boost is found.


[[Imported from SVN: r7424]]

[Bugfix] Prevent definition of HAVE_BOOST without value due to race conditions in some autoconf versions.

For some autoconf versions there was a race condition between ax_boost_base.m4 and dune_boost_base.m4 resulting in HAVE_BOOST being defined with no value (instead of ENABLE_BOOST). For others there were even two definitions of it (one with and one without value). 

This patch renames the symbol being defined in dune_boost_base.m4 to HAVE_DUNE_BOOST and defines a value for it if boost is found.

Please change your code such the preprocessor directives checking for boost from
#if HAVE_BOOST
to
#if HAVE_DUNE_BOOST

Resolves flyspray 1265 and presumably 1249.

[[Imported from SVN: r7422]]

[[Imported from SVN: r7417]]

This commit is related to FS#1257.

[[Imported from SVN: r7394]]

This commit is related to FS#1257.

[[Imported from SVN: r7384]]

[[Imported from SVN: r7129]]

At least since version 3.0 CLang support __cxa_demangle. To support as
many compilers as possible we test for the feature instead of testing
for the compiler version.

Thanks to Andreas Lauser <and@poware.org> for providing this patch
(see FS #1246)

[[Imported from SVN: r7125]]

[[Imported from SVN: r7124]]

I shouldn't be doing patch reviews after 2300

Here is Andreas' commit message:

>From 1049843fa0dbc6b340817b0cd69959e742e80d7a Mon Sep 17 00:00:00 2001
From: Andreas Lauser <Andreas.Lauser@iws.uni-stuttgart.de>
Date: Wed, 6 Feb 2013 23:33:28 +0100
Subject: [PATCH] once again: fix dune_unused.m4

my previous attempt was only partially correct: the compiler did not
chocke because the unused attribute was placed behind the variable,
but because the third argument of AC_TRY_COMPILE is placed inside the
main function. it seems like c++ does not support nested functions, so
the test still failed, leading to the equally undesired result that
DUNE_UNUSED did not have an effect anymore. Mea culpa!

(this time I have at least double verified, that the compiler does not
bail out. last time I probably mis-interpreted the wrong lines as the
output of the dune_unused test in config.log.)


[[Imported from SVN: r7106]]

Thanks to Andreas Lauser for this patch.

Here is his own commit message:

From: Andreas Lauser <and@poware.org>
Date: Mon, 4 Feb 2013 15:34:22 +0100
Subject: [PATCH] fix the test for __attribute__((unused))

it contained two errors which "anihilated" themselfs: the first was a
syntax error in the test itself (the UNUSED macro must be placed
before the identifier of the variable), which caused the compiler to
always return an error. this was compensated by an incorrect
invocation of the AC_TRY_COMPILE macro which featured an empty
argument as third argument instead of the action to be executed if the
test succeeded. this in turn always lead the forth argument (which was
intended by the test to be executed if the test succeeds but was
actually executed if it failed) to be always triggered. In turn this
leads me to the conclusion that DUNE was never compiled using a
compiler which does not support __attribute__((unused)) since this
macro was introduced...


[[Imported from SVN: r7105]]

[[Imported from SVN: r7096]]

[[Imported from SVN: r7088]]

[[Imported from SVN: r7078]]