don't pick it up to build or in dependency list

should be dune_py instead of dune-py

Also: Improve error message in case dependency list parsing ends up with some
weird module name (e.g. empty or ',') by quoting it in the diagnostic output.

It converted to Autotools configure flags to CMake flags.

If you rely on it, add the deleted CMake files to your module.

Since commit 495f2fce USE_MPI was removed from dunecontrol and
the default configuration now defaults to use
parallelism. Unfortunately, there are downstream modules that try to
support multiple versions of DUNE. Sometimes these need to decide
whether to support parallelism before they know which version of DUNE
they are using. This is was not possible when providing
--enable-parallel as no variable gets set for DUNE>=2.4.

With this commit dunecontrol always sets
CMAKE_DISABLE_FIND_PACKAGE_MPI to an appropriate value. Thus if
dunecontrol is used then one can check in one's own module whether the
variable is set explicitly to false and conclude that one is using
>=2.4 and wants parallelism. Otherwise one can check USE_MPI to detect
which behaviour is needed for 2.3.

E.g. like this:
<code>
option (USE_MPI "Use Message Passing Interface for parallel computing" OFF)

if( NOT CMAKE_DISABLE_FIND_PACKAGE_MPI STREQUAL ""
    AND NOT CMAKE_DISABLE_FIND_PACKAGE_MPI)
  set(USE_MPI ON)
endif()

if (NOT USE_MPI)
      set (CMAKE_DISABLE_FIND_PACKAGE_MPI TRUE)
 set (CMAKE_DISABLE_FIND_PACKAGE_MPI TRUE)
endif (NOT USE_MPI)
</code>

Of course without dunecontrol and using the defaults one will still
configure DUNE as parallel, but one's own module as sequential.

In the past MPI / parallel features were disabled until the
proper flag was added. This patch changes the behavior to
enable MPI iff it is found.

* Autotools: --disable-parallel and --enable-parallel work as
  before but the documentation is a bit clumsy to minimize changes.
* CMake: USE_MPI gets removed, too. It was not used by the Dune
  core modules. The backwards compatible --disable-parallel remains.

The UMFPack test has been added after CMake, so I simply
didnt know that it should be placed here, too.

The compatibility layer disabled MPI whenever it did not find
the --enable-parallel flag. This is overeager and harmful if users
are gradually switching to replacing the configure flags with real
cmake flags.

Consider an opts file, with the following content:
CMAKE_FLAGS="-DUSE_MPI=ON"

The compatibility layer would now parse the non-existent CONFIGURE_FLAGS
variable for an --enable-parallel option and disable MPI because it was
not found. The -DCMAKE_DISABLE_FIND_PACKAGE_MPI=TRUE supersedes the USE_MPI=ON
and we get a sequential build.

The fix applied in this patch removes the else clause and only adds
cmake flags when the --enable-parallel flag was found. To still explicitly
allow to force sequential builds, the --disable-parallel flag is parsed
in the same manner.

"Makefile.in", "*.o", etc. need only be listed in the toplevel .gitignore, the
rules are applied recursively.

Test programs etc. should be listed as "/program" in their directory's
.gitignore, so they are not accidentially ignored in a lower level directory.

If duncontrol detects an installed dune-common module, then it always
assumed that it contains a lib/dunecontrol
subdirectory. Unfortunately, this does not hold for older dune-common
modules and dunecontrol will error out later with a message like

/usr/local/lib/dunecontrol: file not found
Execution of dunecontrol terminated due to errors!

With this commit we fix this by actually checking whether the
lib/dunecontrol subdirectoy exists before adding it to
DUNE_CONTROL_PATH.

Thanks a lot to wuhao sife for reporting this problem.

The variable is was set and used by dunecontrol but not by duneproject.

As we have bumped our compiler requirements to GCC 4.4+, we can now
require the compiler to support C++11.

This patch updates both the autotools and the CMake tests to produce an
error if the compiler doesn't support either -std=c++11 or -std=c++0x.

It also renames the tests from ..0X to ..11 and renames the configure
options from --disable-gxx0xcheck to --disable-cxx11check and removes a
couple of redundant calls to the autotools macro.

clang does not support -print-multiarch. Therefore we try to
extract the "Target:" line from clang -v.

This was lost in the last commit.

duneproject failed miserably when run with only installed modules. With
this patch we correctly setup the pkg-config and dunecontrol path to
handle this situation. In addition we fixed various issues with the newly
created modules and they now build as exspected.

Some ^[$BLANK] or [^[$BLANK]^'], where $BLANK is space followed by tab
did not work as a capturing statement in some cases (e.g. opts files
with CONFIGURE_FLAGS="CXX='bla'"). After this patch we use [$NOBLANK]
with NOBLANK=^$space^$tab which works. In addition the other patches
form feature/posix-sed-dunecontrol have been backported to close flyspray
1401.

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.

not available in older bash versions.

[[Imported from SVN: r7462]]

this was the other way around.

[[Imported from SVN: r7458]]

[[Imported from SVN: r7457]]

less interference.

[[Imported from SVN: r7456]]

fix incompatibility with mawk

- explicitly state list of whitespaces
- patch by Ansgar Burchardt

[[Imported from SVN: r7452]]

[[Imported from SVN: r7449]]

translating options for provided for configure to CMake syntax.

[[Imported from SVN: r7448]]