#275 Disable MPI ind configure script by default
Metadata
Property | Value |
---|---|
Reported by | Sven Marnach (sven@pantoffel-wg.de) |
Reported at | Mar 23, 2007 14:12 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
Closed at | Apr 18, 2007 21:48 |
Closed in version | 1.0 |
Resolution | Fixed |
Comment | parallel code is disabled by default (dune-common r4910) |
Description
The parallel code of DUNE should be enabled only by request. Currently, when downloading the tarballs and trying to build DUNE via the dunecontrol script, configure might fail because some MPI implementation is installed but the corresponding daemon does not run. It's not possible to pass configure options conveniently on the dunecontrol command line, so you have to create a dunecontrol.opts file in this case. This doesn't seem very convenient for newbies.
In addition, the current behaviour is quite inconsistent. In the case there isn't any MPI implementation at all, configure won't complain. If there is an MPI implementation, but the daemon is not running, configure aborts with an error message. It would be more natural to simply disable MPI in this case, as it is done if MPI isn't installed at all.