[Dune] Notification from Dune

[Flyspray]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#199 - configure aborts when lam is found but daemon not running
User who did this: - Markus Blatt (mblatt)

----------
I know this annoying, but I always considered this a feature!

The test is trying to run a simple MPI program and this fails if the
daemon
is not running. In this case we cannot be sure that MPI really works.
Therefore 
I think aborting is the right way. Probably a hint to
--disable-mpiruntest would
be handy.

Another option would be to say MPI is not working and just configure
dune without MPI.
This will have side effects, too:

Consider compiling on the front node of cluster. Usually it is not
allowed to run MPI programs
there. Ergo, one would compile dune without MPI. Put the program in
the queuing system and after 1
week of waiting for a computing spot would just get an error message
back that this was no MPI program.

I think many people including myself will not be amused about this
behaviour!

In  my opinion the current procedure is the preferable one.
----------

More information can be found at the following URL:
http://hal.iwr.uni-heidelberg.de/flyspray/?do=details&id=199#comment198

You are receiving this message because you have requested it from the
Flyspray bugtracking system.  You can be removed from future
notifications by visiting the URL shown above.