When copying PoolAllocators Bard experienced linking errors to the
copy constructor of Pool, which is deactivated. To fix this we added
the copy constructor. Note that it does not copy the pool such that
ownership of allocated memory chunks is clear.

Kudos go to Bard for noticing this and providing the fix.

In addition we removed the copy constructor of the specialization for
void as the default coy constructor suffices.

Its call was removed from dune_mpi.m4 back in 2012.

The warning with more then one job was: "make[1]: warning:
jobserver unavailable: using -j1. Add `+' to parent make rule."
Still, I get no speedup for -jN with N > 1.

Deprecate header and macro dune_static_assert.
Use static_assert instead.

They cased compiler warnings.

DUNE_FINAL is a helper macro for C++11 and should be placed in
std, where now all compatibility has to be placed.
Beautify Doxygen documentation.

sadly the touchpad added some arbitrary "pwd; ", which slipped my
test, as I don't use cmake. Thanks to Andi Buhr for pointing this out.

up to now you could specify a BUILDDIR variable, which implied that modules were built in
$srdir/$BUILDDIR.
Imagine you have your dune modules in $HOME/Src. When you set BUILDDIR=build.g++
your dune-common module is built in $HOME/Src/dune-common/build.g++
Now you change BUILDDIR to an absolute path, e.g. BUILDDIR=$HOME/Build.g++
With the latest change dunecontrol will now build dune-common in
$HOME/Build.g++/dune-common/

Thanks to Angar for bugging me :-)

This patch adds an AutoTools test that tests whether the compiler
supports the 'final' keyword.  It defines the DUNE_FINAL preprocessor
macro, which expands to 'final' if the keyword is supported, and
is empty otherwise.

kudos to Elias Pipping, for details see (FS #1166)
as the new Dune requirements are >= g++ 4.4 we are sure that initializer_list is available.

we install dune.complete into $PREFIX/share/bash-complete/
upto now you have to source the file by hand.

Module names with hyphens are no longer changed to
underscores.
This fixes FS#1432.

Previously running the installed mpi-config failed as mpi-config.m4
was not found. This patch corrects the path to it in the script and
fixes the problem.