On Jan 16, 2006, at 11:32 AM, Yves Reymen wrote:
> Recently openmpi v1.0.1 was installed on our cluster. It contains all
> parameters of ompi_config.h within a #ifndef OMPI_CONFIG_H. I am
> wondering how it is possible to give one of these parameters an other
> value after everthing is configured and installed, given the fact that
> no ompi_config.h is present in the installation.
> Take for instance the OMPI_WANT_CXX_BINDINGS that decides if you
> want to
> include de C++ bindings in mpicxx.h or not. If I set it on my compile
> line as -DOMPI_WANT_CXX_BINDINGS=0. It will always be redefined to the
> value in mpi.h, which for our installation is 1.
> Is there a way of getting rid of this redefinition?
Your only options are to live with the defaults installed or re-
configure with the values you want. For this one value, you could
probably safely edit the #define for OMPI_WANT_CXX_BINDINGS in mpi.h,
but that would only work in this one scenario, and even then, would
prevent the use of the C++ bindings with that install.
We generally don't allow for overriding those configure options
because in almost all cases, it won't result in what the user
expects. For instance, if the value for WANT_CXX_BINDINGS is set to
0 by configure, and the user tries to set it to 1, the headers and
libraries required for the C++ bindings won't be present. Or if you
tried to change the WANT_EXCEPTIONS value from 0 to 1, code not built
to handle exceptions might suddenly be expected to do so, resulting
in very bad things.
Is there a reason that you want to disable the C++ bindings after
installation? They should be absolutely harmless if you aren't using
them. If that isn't the case, then we need to fix whatever is
causing your problems.
Open MPI developer