openmpi/opal/mca/crs/none/configure.params

# -*- shell-script -*-
#
# Copyright (c) 2004-2008 The Trustees of Indiana University.
#                         All rights reserved.
# $COPYRIGHT$
# 
# Additional copyrights may follow
# 
# $HEADER$
#

PARAM_INIT_FILE=crs_none_component.c
PARAM_CONFIG_FILES="Makefile"
This commit fixes runs when there is no available CRS component (BLCR is unavailable, and SELF is deactivated). Previously the run would fail out of MPI_INIT since the OPAL CRS framework could not select a component. This is because the framework did not recognize the 'none' component as a full component because it was part of crs/base. I promoted the ''none'' component to a full component, and updated the other components to reflect this code movement. The ''none'' component is the default component unless the user requests '''-am ft-enable-cr''' to auto-select a component. There is an MCA parameter to show a warning if the application requested an FT enabled job, but the ''none'' component was selected ({{{crs_none_select_warning}}}). This temporarily fixes the problem mentioned in r18739. The full fix will entail working on ticket #1291. Thanks to Ethan from Sun for finding this bug. This commit was SVN r18840. The following SVN revision numbers were found above: r18739 --> open-mpi/ompi@a003fa7a5077c42ce7a4427ac26a9714152729a1 2008-07-08 20:04:39 +00:00			`# -- shell-script --`
			`#`
			`# Copyright (c) 2004-2008 The Trustees of Indiana University.`
			`# All rights reserved.`
			`# $COPYRIGHT$`
			`#`
			`# Additional copyrights may follow`
			`#`
			`# $HEADER$`
			`#`

			`PARAM_INIT_FILE=crs_none_component.c`
			`PARAM_CONFIG_FILES="Makefile"`