Skip to content

Commit fe482ad

Browse files
committed
Scope "result" variable in options
result is commonly used as a scoped variable throughout OMPI's configure. This doesn't currently cause failures, because the assembly checks unconditionally unset result (after using it for its own things). But to clean up the assembly macros, we must clean up this usage. Signed-off-by: Brian Barrett <[email protected]>
1 parent 053ce66 commit fe482ad

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

config/opal_configure_options.m4

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -420,6 +420,7 @@ AM_CONDITIONAL([OPAL_WANT_SCRIPT_WRAPPER_COMPILERS], [test "$enable_script_wrapp
420420
#
421421
# Support per-user config files?
422422
#
423+
OPAL_VAR_SCOPE_PUSH([result])
423424
AC_ARG_ENABLE([per-user-config-files],
424425
[AS_HELP_STRING([--enable-per-user-config-files],
425426
[Disable per-user configuration files, to save disk accesses during job start-up. This is likely desirable for large jobs. Note that this can also be achieved by environment variables at run-time. (default: enabled)])])
@@ -430,6 +431,7 @@ else
430431
fi
431432
AC_DEFINE_UNQUOTED([OPAL_WANT_HOME_CONFIG_FILES], [$result],
432433
[Enable per-user config files])
434+
OPAL_VAR_SCOPE_POP
433435

434436
#
435437
# Do we want to enable IPv6 support?

0 commit comments

Comments
 (0)