spline: some fixes to make Spline::intersect() work correctly

most of these issues are fallout from the conversion of the spline
class from a moments (second derivative) based approach to hermite
base functions:

- the second and third derivatives where incorrect, and the third
  derivative was not available in the public interface.
- The unit test did not check the derivatives
- The coefficients for the monomial basis were off by the factors
  stemming from the derivatives
- The intersectIntervall_() method used std::max() instead of
  std::min() at one place and still added the base offset for the x
  values as indicated by Stoer
spline: fix the monotinic_() method and creation of monotonic splines

also, extend the unit test for it. (*phew* that was much more fun than
appreciated because of all the index shifts. I'm still not 100% sure
that everything works in all corner cases, but at least my confidence
is at 95%.)
fix test for HAVE_QUAD on some instances of ubuntu 13.10

I haven't figured out why this happens, but on one of my computers
running kubuntu 13.10 g++ says the following if one tries to use
quadruple precision math:

/home/erne/src/ewoms/ewoms/common/quad.hh: In static member function ‘static quad std::numeric_limits<__float128>::min()’:
/home/erne/src/ewoms/ewoms/common/quad.hh:52:14: error: unable to find numeric literal operator ‘operator"" Q’
     { return FLT128_MIN; }

since this happens only on this machine and only with the c++ (but
not the C) compiler, i suppose that this is either an upgrade issue
with kubuntu or an issue with the ubuntu gcc stack. Strangely enough,
my other kubuntu machine does not have a problem with that...

In any case also testing for assignability of constants and using the
C++ compiler for the quadmath test won't hurt...
spline: avoid bogous "might be used uninitialized" compiler warning on GCC
Merge pull request #428 from andlaus/make_quadmath_test_more_strict

fix test for HAVE_QUAD on some instances of ubuntu 13.10
Output newline after last entry before "/" when outputting grid to file. This make gridfile more robust for later usage.
build system: prevent endless loop when using dunecontrol

this seems to be a bug in cmake 2.8.10.2: if the user sets the
CMAKE_CXX_COMPILER variable for a build directory where this variable
has already been set, one gets an endless loop. This stings especially
if using the dunecontrol compatibility layer as the compiler flags are
unconditionally set via the CXX_FLAGS environment variable in the
options file. Running duncontrol on a module twice will thus trigger the
infinite loop if some compiler flags are set by the user.

The solution is relatively simple: Delete the CMakeFiles directory
before calling cmake. for the dunecontrol compatibility mode, we do
this in the configure script. For details about the cmake bug, see
http://www.cmake.org/Bug/view.php?id=14119
fixup! spline: avoid bogous "might be used uninitialized" compiler warning on GCC
Merge pull request #427 from andlaus/fix_spline

spline: some fixes to make Spline::intersect() work correctly
Merge pull request #429 from karbor/master

Output newline after last entry before "/" when outputting grid to file....
configure script: also delete the cmake cache

This replicates the autotools behavior and was suggested by Roland
Kaufmann.
Extract common parts of blackoil and incomp. state

Put the identical parts of the simulator state into a base class that
they can be referenced from when adressing the common fields.
configure script: add a stub implementation for the --config-cache argument

so far, it is only a flag which prevents the cache from being
deleted. To warn the user about a potential infinite loop, a warning
is printed if this flag was specified and some compiler or some compiler
flags were set by the user. This idea was proposed by Roland Kaufmann.
outputField(): Parametrise number of items per line

This is in preparation of leveraging the outputField() helper for
printing COORD and ZCORN too.
writeGrdecl(): Use outputField() for COORD and ZCORN

This leverages the "number-of-items-per-line" parameter introduced
in commit 608d4c1.
outputField(): Use straight-line code

There is no need to use a nested loop to output a constant number of
items per line.  We only need to output a '\n' rather than a ' '
after every "nl" item output.
Remove long-disabled code

The code to condense the output using repeat counts was disabled
long ago (commit fc992da).  If we ever need this feature, we can
bring it back from history or reimplemented in a refined fashion.
Changed the check_cxx_source_compiles() in Findopm-parser to look for Deck.hpp; Parser.hpp had uneccasary complicated interaction with cJSON
Merge pull request #432 from joakim-hove/find-opm-parser

CMAKE: check_cxx_source_compiles() in Findopm-parser to look for Deck.hpp
Merge pull request #431 from bska/simplify-cpchop-output

CornerPointChopper: Tidy code to output GRDECL format of subsample