Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] Should visibility and memchecker abort configure?
From: Ralf Wildenhues (Ralf.Wildenhues_at_[hidden])
Date: 2008-10-05 05:15:48


if you allow me my 2 cents:

At configure time, it is possible to distinguish between several
different user inputs:
- the user typed --enable-foo,
- the user typed --disable-foo or --enable-foo=no,
- the user typed --enable-foo=ARG (ARG is available for further
- the user used none of the above.

IIUC you have already sorted out the visibility issue by using the last,
and the memchecker issue is about having an incompatible version
installed. One typical semantics would be to not try to use the feature
at all if --disable-foo was explicitly passed.

Hope that helps.