The warning was added before FS#493 and the related FS#491
were resolved. Probably it was just forgotten to remove the
warning.
I double checked with GCC 5 and -O3. Works for me.

Probably an error caused during merging.

Nothing needs to be included with proper C++11 compilers.

Old feature support macros which were tested until 2.4, kept around
for one more release. As these are now always supported due to the
new compiler requirements, they are directly defined without an
explicit test.

As documented, tranformTuple should support AddRefTypeEvaluator. As
std::make_tuple will remove references (using std::decay) from the
funtor's return type, the returned tuple would contain copies of the
values. This is not the intended behavior.

This patch adds AddRefTypeEvaluator to the utilitytest and fixes the
return type of transformTuple.

These commits 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 commits 0f12caff
and d75c3a46.

This reverts commit 4441ec26.
The minimal required is finally GCC 4.7 or newer (it is actuall 4.9).
Original commit message for d26e5ed3 was
    [C++11] Follow the C++11 specification of operator new.

    The signature changed in C++11 which we require now.
    To get more details see the mailinglost in October 2012.

Otherwise FieldVector<K,1> is not literal and its size()
method can never be used as constexpr.

This makes the code more robust and (a bit) more robust.  Additionally,
it repairs the recent breakage that I introduced by modifying promotiontraits.hh.

Otherwise FieldVector is not a literal type and
calling its size() method is not a const-expression
although size() itself is declared as constexpr.

The previous implementation consisted of a list of promotion rules for
various types.  The new implementation is much shorter and more general:
it will also work for types not on the old list.  The promoted type is
now defined as the result type of the addition of the two input types.
There is no special reason to use addition here, but it does reproduce
the precise behavior of the old implementation.

Document an incompatibility issue of index_sequence
and add a reminder to fix this as soon as we allow
template aliases.
This can only be fixed

This does not apply cleanly to the release.

by testing whether we work on a end iterator. In this case the distance
function will fail. Found that out by gcc's stdlib with debugging turned on.

... and don't take absolute value of comparison result.
Thanks to Max Kahnt for reporting this.

Otherwise it won't appear in the doxygen documentation

Add missing files, remove ancient buildsystem stuff and stuff where it is
unclear where it comes from.

[test][typetraits][warnings] Split the test for deprecated functionality in typetraits.hh into its own testcase.  That way I can simply disable deprecation warnings there.

There was a mechanism with apparently similar goal involving the define
DISABLE_DEPRECATED_METHOD_CHECKS.  However, I could not figure out how that
was intended to work, the only occurances of DISABLE_DEPRECATED_METHOD_CHECKS
were in typetraitstest.hh.  Probably you were supposed to set that define by
hand in your CPPFLAGS, which I consider unacceptable.

The section is empty since the code was split into the dune-geometry
module.

Since fda5a9e0 AlignmentOf always uses
std::alignment_of and the fallback implementation is no longer used.

It's more CMake style.