2016-04-26 15:56:37 +03:00
|
|
|
# -*- shell-script -*-
|
|
|
|
|
#
|
2019-12-24 21:18:46 +03:00
|
|
|
# Copyright (c) 2009-2019 Cisco Systems, Inc. All rights reserved
|
2017-06-22 07:10:35 +03:00
|
|
|
# Copyright (c) 2014-2017 Intel, Inc. All rights reserved.
|
2018-07-11 05:26:37 +03:00
|
|
|
# Copyright (c) 2015-2018 Research Organization for Information Science
|
2016-04-26 15:56:37 +03:00
|
|
|
# and Technology (RIST). All rights reserved.
|
|
|
|
|
# Copyright (c) 2016 Los Alamos National Security, LLC. All rights
|
|
|
|
|
# reserved.
|
|
|
|
|
#
|
|
|
|
|
# $COPYRIGHT$
|
|
|
|
|
#
|
|
|
|
|
# Additional copyrights may follow
|
|
|
|
|
#
|
|
|
|
|
# $HEADER$
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Priority
|
|
|
|
|
#
|
2019-12-24 21:18:46 +03:00
|
|
|
AC_DEFUN([MCA_opal_hwloc_hwloc2_PRIORITY], [80])
|
2016-04-26 15:56:37 +03:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Force this component to compile in static-only mode
|
|
|
|
|
#
|
2019-12-24 21:18:46 +03:00
|
|
|
AC_DEFUN([MCA_opal_hwloc_hwloc2_COMPILE_MODE], [
|
2016-04-26 15:56:37 +03:00
|
|
|
AC_MSG_CHECKING([for MCA component $2:$3 compile mode])
|
|
|
|
|
$4="static"
|
|
|
|
|
AC_MSG_RESULT([$$4])
|
|
|
|
|
])
|
|
|
|
|
|
|
|
|
|
# Include hwloc m4 files
|
2019-12-24 21:18:46 +03:00
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/hwloc.m4)
|
|
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/hwloc_pkg.m4)
|
|
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/hwloc_check_attributes.m4)
|
|
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/hwloc_check_visibility.m4)
|
|
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/hwloc_check_vendor.m4)
|
|
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/hwloc_components.m4)
|
|
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/hwloc_internal.m4)
|
|
|
|
|
m4_include(opal/mca/hwloc/hwloc2/hwloc/config/netloc.m4)
|
|
|
|
|
|
|
|
|
|
# MCA_hwloc_hwloc2_POST_CONFIG()
|
2016-04-26 15:56:37 +03:00
|
|
|
# ---------------------------------
|
2019-12-24 21:18:46 +03:00
|
|
|
AC_DEFUN([MCA_opal_hwloc_hwloc2_POST_CONFIG],[
|
|
|
|
|
OPAL_VAR_SCOPE_PUSH([opal_hwloc_hwloc2_basedir])
|
2016-04-26 15:56:37 +03:00
|
|
|
|
|
|
|
|
# If we won, then do all the rest of the setup
|
2019-12-24 21:18:46 +03:00
|
|
|
AS_IF([test "$1" = "1" && test "$opal_hwloc_hwloc2_support" = "yes"],
|
2016-04-26 15:56:37 +03:00
|
|
|
[
|
|
|
|
|
# Set this variable so that the framework m4 knows what
|
2017-02-10 15:48:43 +03:00
|
|
|
# file to include in opal/mca/hwloc/hwloc-internal.h
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_basedir=opal/mca/hwloc/hwloc2
|
|
|
|
|
opal_hwloc_base_include="$opal_hwloc_hwloc2_basedir/hwloc2.h"
|
2016-04-26 15:56:37 +03:00
|
|
|
|
|
|
|
|
# Add some stuff to CPPFLAGS so that the rest of the source
|
|
|
|
|
# tree can be built
|
2019-12-24 21:18:46 +03:00
|
|
|
file=$opal_hwloc_hwloc2_basedir/hwloc
|
2016-09-22 17:39:22 +03:00
|
|
|
CPPFLAGS="-I$OPAL_TOP_SRCDIR/$file/include $CPPFLAGS"
|
2016-04-26 15:56:37 +03:00
|
|
|
AS_IF([test "$OPAL_TOP_BUILDDIR" != "$OPAL_TOP_SRCDIR"],
|
2016-09-22 17:39:22 +03:00
|
|
|
[CPPFLAGS="-I$OPAL_TOP_BUILDDIR/$file/include $CPPFLAGS"])
|
2016-04-26 15:56:37 +03:00
|
|
|
unset file
|
|
|
|
|
])
|
|
|
|
|
OPAL_VAR_SCOPE_POP
|
|
|
|
|
|
|
|
|
|
# This must be run unconditionally
|
|
|
|
|
HWLOC_DO_AM_CONDITIONALS
|
|
|
|
|
])dnl
|
|
|
|
|
|
|
|
|
|
|
2019-12-24 21:18:46 +03:00
|
|
|
# MCA_hwloc_hwloc2_CONFIG([action-if-found], [action-if-not-found])
|
2016-04-26 15:56:37 +03:00
|
|
|
# --------------------------------------------------------------------
|
2019-12-24 21:18:46 +03:00
|
|
|
AC_DEFUN([MCA_opal_hwloc_hwloc2_CONFIG],[
|
|
|
|
|
AC_CONFIG_FILES([opal/mca/hwloc/hwloc2/Makefile])
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
|
2019-12-24 21:18:46 +03:00
|
|
|
OPAL_VAR_SCOPE_PUSH([HWLOC_VERSION opal_hwloc_hwloc2_save_CPPFLAGS opal_hwloc_hwloc2_save_LDFLAGS opal_hwloc_hwloc2_save_LIBS opal_hwloc_hwloc2_save_cairo opal_hwloc_hwloc2_save_xml opal_hwloc_hwloc2_save_mode opal_hwloc_hwloc2_basedir opal_hwloc_hwloc2_file opal_hwloc_hwloc2_save_cflags CPPFLAGS_save LIBS_save opal_hwloc_external])
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
|
2018-08-08 19:58:49 +03:00
|
|
|
# We know that the external hwloc component will be configured
|
|
|
|
|
# before this one because of its priority. This component is only
|
|
|
|
|
# needed if the external component was not successful in selecting
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
# itself. Print out a message explaining this.
|
2018-08-08 19:58:49 +03:00
|
|
|
AC_MSG_CHECKING([if hwloc external component succeeded])
|
|
|
|
|
AS_IF([test "$opal_hwloc_external_support" = "yes"],
|
|
|
|
|
[AC_MSG_RESULT([yes])
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
AC_MSG_NOTICE([hwloc:external succeeded, so this component will be configured, but then will be skipped])],
|
2018-08-08 19:58:49 +03:00
|
|
|
[AC_MSG_RESULT([no])
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
AC_MSG_NOTICE([hwloc:external failed, so this component will be used])])
|
2016-04-26 15:56:37 +03:00
|
|
|
|
|
|
|
|
# default to this component not providing support
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_basedir=opal/mca/hwloc/hwloc2
|
|
|
|
|
opal_hwloc_hwloc2_support=no
|
2016-04-26 15:56:37 +03:00
|
|
|
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_save_CPPFLAGS=$CPPFLAGS
|
|
|
|
|
opal_hwloc_hwloc2_save_LDFLAGS=$LDFLAGS
|
|
|
|
|
opal_hwloc_hwloc2_save_LIBS=$LIBS
|
2016-07-06 05:59:51 +03:00
|
|
|
|
|
|
|
|
# save XML or graphical options
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_save_cairo=$enable_cairo
|
|
|
|
|
opal_hwloc_hwloc2_save_xml=$enable_xml
|
|
|
|
|
opal_hwloc_hwloc2_save_static=$enable_static
|
|
|
|
|
opal_hwloc_hwloc2_save_shared=$enable_shared
|
|
|
|
|
opal_hwloc_hwloc2_save_plugins=$enable_plugins
|
|
|
|
|
opal_hwloc_hwloc2_save_mode=$hwloc_mode
|
2016-07-06 05:59:51 +03:00
|
|
|
|
|
|
|
|
# never enable hwloc's graphical option
|
|
|
|
|
enable_cairo=no
|
|
|
|
|
|
|
|
|
|
# never enable hwloc's plugin system
|
|
|
|
|
enable_plugins=no
|
|
|
|
|
enable_static=yes
|
|
|
|
|
enable_shared=no
|
|
|
|
|
|
|
|
|
|
# Override -- disable hwloc's libxml2 support, but enable the
|
|
|
|
|
# native hwloc XML support
|
|
|
|
|
enable_libxml2=no
|
|
|
|
|
enable_xml=yes
|
|
|
|
|
|
2017-06-22 07:10:35 +03:00
|
|
|
# ensure we are in "embedded" mode
|
|
|
|
|
hwloc_mode=embedded
|
|
|
|
|
|
2017-09-21 18:25:46 +03:00
|
|
|
# GL and OpenCL OS devices aren't used in OMPI
|
|
|
|
|
enable_gl=no
|
|
|
|
|
enable_opencl=no
|
|
|
|
|
|
2017-10-04 21:23:15 +03:00
|
|
|
# Per https://github.com/open-mpi/ompi/pull/4257, ALWAYS
|
|
|
|
|
# disable cuda support
|
2017-09-24 15:36:23 +03:00
|
|
|
enable_cuda=no
|
|
|
|
|
|
|
|
|
|
# Open MPI currently does not use hwloc's NVML support
|
|
|
|
|
enable_nvml=no
|
2017-04-05 05:07:07 +03:00
|
|
|
|
2016-07-06 05:59:51 +03:00
|
|
|
# hwloc checks for compiler visibility, and its needs to do
|
|
|
|
|
# this without "picky" flags.
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_save_cflags=$CFLAGS
|
2016-07-06 05:59:51 +03:00
|
|
|
CFLAGS=$OPAL_CFLAGS_BEFORE_PICKY
|
2017-04-05 05:46:22 +03:00
|
|
|
AS_IF([test -n "$opal_datatype_cuda_CPPFLAGS"],
|
|
|
|
|
[CPPFLAGS="$CPPFLAGS $opal_datatype_cuda_CPPFLAGS"])
|
|
|
|
|
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
# Only set the symbol prefix if this component is being used
|
|
|
|
|
# (i.e., if the external component is not being used).
|
|
|
|
|
AS_IF([test "$opal_hwloc_external_support" = "no"],
|
2019-12-24 21:18:46 +03:00
|
|
|
[HWLOC_SET_SYMBOL_PREFIX([opal_hwloc2_])])
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
|
|
|
|
|
# Do the bulk of the hwloc core setup
|
2019-12-24 21:18:46 +03:00
|
|
|
HWLOC_SETUP_CORE([opal/mca/hwloc/hwloc2/hwloc],
|
2016-07-06 05:59:51 +03:00
|
|
|
[AC_MSG_CHECKING([whether hwloc configure succeeded])
|
|
|
|
|
AC_MSG_RESULT([yes])
|
2019-12-24 21:18:46 +03:00
|
|
|
HWLOC_VERSION="internal v`$srcdir/$opal_hwloc_hwloc2_basedir/hwloc/config/hwloc_get_version.sh $srcdir/$opal_hwloc_hwloc2_basedir/hwloc/VERSION`"
|
2016-07-06 05:59:51 +03:00
|
|
|
|
|
|
|
|
# Build flags for our Makefile.am
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_LDFLAGS='$(HWLOC_EMBEDDED_LDFLAGS)'
|
|
|
|
|
opal_hwloc_hwloc2_LIBS='$(OPAL_TOP_BUILDDIR)/'"$opal_hwloc_hwloc2_basedir"'/hwloc/hwloc/libhwloc_embedded.la $(HWLOC_EMBEDDED_LIBS)'
|
|
|
|
|
opal_hwloc_hwloc2_support=yes
|
2016-07-06 05:59:51 +03:00
|
|
|
|
2019-12-24 21:18:46 +03:00
|
|
|
AC_DEFINE_UNQUOTED([HWLOC_HWLOC2_HWLOC_VERSION],
|
2016-07-06 05:59:51 +03:00
|
|
|
["$HWLOC_VERSION"],
|
|
|
|
|
[Version of hwloc])
|
|
|
|
|
|
|
|
|
|
# Do we have verbs support?
|
|
|
|
|
CPPFLAGS_save=$CPPFLAGS
|
|
|
|
|
AS_IF([test "$opal_want_verbs" = "yes"],
|
|
|
|
|
[CPPFLAGS="-I$opal_verbs_dir/include $CPPFLAGS"])
|
|
|
|
|
AC_CHECK_HEADERS([infiniband/verbs.h])
|
|
|
|
|
CPPFLAGS=$CPPFLAGS_save
|
|
|
|
|
],
|
|
|
|
|
[AC_MSG_CHECKING([whether hwloc configure succeeded])
|
|
|
|
|
AC_MSG_RESULT([no])
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_support=no])
|
|
|
|
|
CFLAGS=$opal_hwloc_hwloc2_save_cflags
|
2016-07-06 05:59:51 +03:00
|
|
|
|
|
|
|
|
# Restore some env variables, if necessary
|
2019-12-24 21:18:46 +03:00
|
|
|
AS_IF([test -n "$opal_hwloc_hwloc2_save_cairo"],
|
|
|
|
|
[enable_cairo=$opal_hwloc_hwloc2_save_cairo])
|
|
|
|
|
AS_IF([test -n "$opal_hwloc_hwloc2_save_xml"],
|
|
|
|
|
[enable_xml=$opal_hwloc_hwloc2_save_xml])
|
|
|
|
|
AS_IF([test -n "$opal_hwloc_hwloc2_save_static"],
|
|
|
|
|
[enable_static=$opal_hwloc_hwloc2_save_static])
|
|
|
|
|
AS_IF([test -n "$opal_hwloc_hwloc2_save_shared"],
|
|
|
|
|
[enable_shared=$opal_hwloc_hwloc2_save_shared])
|
|
|
|
|
AS_IF([test -n "$opal_hwloc_hwloc2_save_plugins"],
|
|
|
|
|
[enable_plugins=$opal_hwloc_hwloc2_save_shared])
|
|
|
|
|
|
|
|
|
|
CPPFLAGS=$opal_hwloc_hwloc2_save_CPPFLAGS
|
|
|
|
|
LDFLAGS=$opal_hwloc_hwloc2_save_LDFLAGS
|
|
|
|
|
LIBS=$opal_hwloc_hwloc2_save_LIBS
|
|
|
|
|
|
|
|
|
|
AC_SUBST([opal_hwloc_hwloc2_CFLAGS])
|
|
|
|
|
AC_SUBST([opal_hwloc_hwloc2_CPPFLAGS])
|
|
|
|
|
AC_SUBST([opal_hwloc_hwloc2_LDFLAGS])
|
|
|
|
|
AC_SUBST([opal_hwloc_hwloc2_LIBS])
|
2016-07-06 05:59:51 +03:00
|
|
|
|
|
|
|
|
# Finally, add some flags to the wrapper compiler so that our
|
|
|
|
|
# headers can be found.
|
2019-12-24 21:18:46 +03:00
|
|
|
hwloc_hwloc2_WRAPPER_EXTRA_LDFLAGS="$HWLOC_EMBEDDED_LDFLAGS"
|
|
|
|
|
hwloc_hwloc2_WRAPPER_EXTRA_LIBS="$HWLOC_EMBEDDED_LIBS"
|
|
|
|
|
hwloc_hwloc2_WRAPPER_EXTRA_CPPFLAGS='-I${pkgincludedir}/'"$opal_hwloc_hwloc2_basedir/hwloc/include"
|
2016-04-26 15:56:37 +03:00
|
|
|
|
2016-07-04 11:01:35 +03:00
|
|
|
# If we are not building the internal hwloc, then indicate that
|
|
|
|
|
# this component should not be built. NOTE: we still did all the
|
|
|
|
|
# above configury so that all the proper GNU Autotools
|
|
|
|
|
# infrastructure is setup properly (e.g., w.r.t. SUBDIRS=hwloc in
|
|
|
|
|
# this directory's Makefile.am, we still need the Autotools "make
|
|
|
|
|
# distclean" infrastructure to work properly).
|
hwloc201/configure.m4: make it safe when used with hwloc:external
The Autoconf AC_CONFIG_* macros can only be instantiated exacly once
for any given file, *and* they must be in a code execution path at run
time for the target file to be generated at the end of configure.
For example, if you want to generate file ABC at the end of configure,
you must invoke the AC_CONFIG_FILES(ABC) macro in a code path that
will get executed when configure is run.
That's pretty straightforward.
What's not straightforward is two corner cases:
1. You cannot invoke the AC_CONFIG_FILES(ABC) macro for the same file
more than once. If you do, autoreconf will fail (even before you
can run configure).
2. If AC_CONFIG_FILES(ABC) is not in a code path that is executed by
configure, the file ABC is not registered properly, and ABC will
not be generated at the end of configure.
This applies to hwloc because hwloc's HWLOC_SETUP_CORE macro calls
both AC_CONFIG_FILES and AC_CONFIG_HEADER to setup its Makefiles
(etc.) so that targets like "make distclean" and "make distcheck" will
work properly. Hence, we *have* to invoke HWLOC_SETUP_CORE.
However, the MCA_opal_hwloc_hwloc201_CONFIG macro has a few side
effects. It would be nice to do able to do something like this:
```
if hwloc:extern is going to be used:
Invoke minimal HWLOC_SETUP_CORE (with no side effects)
else
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
But we can't, because autoreconf will detect that AC_CONFIG_FILES has
been invoked on the same files more than once (regardless of whether
those code paths will be executed at run time or not). Kaboom.
Similarly, we can't do this:
```
if hwloc:extern is not going to be used:
Invoke full HWLOC_SETUP_CORE (with side effects)
fi
```
Because then hwloc's AC_CONFIG_FILES won't be registered properly when
hwloc:external *is* used (i.e., when the HWLOC_SETUP_CORE macro is not
in a code path that is executed at run time), and targets like "make
distclean" will fail because hwloc's Makefiles won't have been setup.
Kaboom.
But remember that the hwloc framework is a bit special: there will
only ever be 2 comoponents: external and internal. External is
guaranteed to be configured first because of its priority. So the
internal component (i.e., this component) immediately knows if it is
going to be used or not based on whether the external component
configuration succeeded or failed.
Specifically: regardless of whether the internal component (i.e., this
component) is going to be used, we have to invoke HWLOC_SETUP_CORE.
But we can manage the side effects: allow the side effects when
this/internal component is going to be used, and avoid the side
effects when this/internal component is not going to be used.
This is a little less clean than I would have liked, but because of
Autoconf's oddity about its AC_CONFIG_* macros, this is the only
solution I could come up with.
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
2018-08-11 16:04:06 +03:00
|
|
|
AS_IF([test "$opal_hwloc_external_support" = "yes"],
|
|
|
|
|
[AC_MSG_NOTICE([using an external hwloc; disqualifying this component])
|
2019-12-24 21:18:46 +03:00
|
|
|
opal_hwloc_hwloc2_support=no],
|
2017-03-01 07:36:08 +03:00
|
|
|
[AC_DEFINE([HAVE_DECL_HWLOC_OBJ_OSDEV_COPROC], [1])
|
|
|
|
|
AC_DEFINE([HAVE_HWLOC_TOPOLOGY_DUP], [1])])
|
2016-07-04 11:01:35 +03:00
|
|
|
|
2016-04-26 15:56:37 +03:00
|
|
|
# Done!
|
2019-12-24 21:18:46 +03:00
|
|
|
AS_IF([test "$opal_hwloc_hwloc2_support" = "yes"],
|
2016-04-26 15:56:37 +03:00
|
|
|
[$1],
|
|
|
|
|
[$2])
|
|
|
|
|
|
|
|
|
|
OPAL_VAR_SCOPE_POP
|
|
|
|
|
])dnl
|