Merge branch 'backport-ci-fedora-39' into ci-fedora-39

Modules/CheckCCompilerFlag.cmake

@@ -22,7 +22,7 @@ issue a diagnostic message when given the flag.  Whether the flag has any
 effect or even a specific one is beyond the scope of this module.
 
 The check is only performed once, with the result cached in the variable named
-by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
 rather than performing the check again, even if the ``<code>`` changes. In
 order to force the check to be re-evaluated, the variable named by
 ``<resultVar>`` must be manually removed from the cache.

Modules/CheckCSourceCompiles.cmake

@@ -23,7 +23,7 @@ Check if given C source compiles and links into an executable.
   expressions.
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckCSourceRuns.cmake

@@ -22,7 +22,7 @@ subsequently be run.
   false (e.g. an empty string or an error message).
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckCXXSourceCompiles.cmake

@@ -23,7 +23,7 @@ Check if given C++ source compiles and links into an executable.
   expressions.
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckCXXSourceRuns.cmake

@@ -22,7 +22,7 @@ subsequently be run.
   false (e.g. an empty string or an error message).
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckCompilerFlag.cmake

@@ -23,7 +23,7 @@ issue a diagnostic message when given the flag.  Whether the flag has any
 effect or even a specific one is beyond the scope of this module.
 
 The check is only performed once, with the result cached in the variable named
-by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
 rather than performing the check again, even if the ``<code>`` changes. In
 order to force the check to be re-evaluated, the variable named by
 ``<resultVar>`` must be manually removed from the cache.

Modules/CheckFortranCompilerFlag.cmake

@@ -24,7 +24,7 @@ issue a diagnostic message when given the flag.  Whether the flag has any
 effect or even a specific one is beyond the scope of this module.
 
 The check is only performed once, with the result cached in the variable named
-by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
 rather than performing the check again, even if the ``<code>`` changes. In
 order to force the check to be re-evaluated, the variable named by
 ``<resultVar>`` must be manually removed from the cache.

Modules/CheckFortranSourceCompiles.cmake

@@ -48,7 +48,7 @@ Check if given Fortran source compiles and links into an executable.
   ``.F90`` is a typical choice.
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckFortranSourceRuns.cmake

@@ -44,7 +44,7 @@ subsequently be run.
   ``SRC_EXT`` option can be used to override this with ``.<extension>`` instead.
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckOBJCCompilerFlag.cmake

@@ -24,7 +24,7 @@ issue a diagnostic message when given the flag.  Whether the flag has any
 effect or even a specific one is beyond the scope of this module.
 
 The check is only performed once, with the result cached in the variable named
-by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
 rather than performing the check again, even if the ``<code>`` changes. In
 order to force the check to be re-evaluated, the variable named by
 ``<resultVar>`` must be manually removed from the cache.

Modules/CheckOBJCSourceCompiles.cmake

@@ -25,7 +25,7 @@ Check if given Objective-C source compiles and links into an executable.
   expressions.
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckOBJCSourceRuns.cmake

@@ -24,7 +24,7 @@ subsequently be run.
   false (e.g. an empty string or an error message).
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckOBJCXXCompilerFlag.cmake

@@ -24,7 +24,7 @@ issue a diagnostic message when given the flag.  Whether the flag has any
 effect or even a specific one is beyond the scope of this module.
 
 The check is only performed once, with the result cached in the variable named
-by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
 rather than performing the check again, even if the ``<code>`` changes. In
 order to force the check to be re-evaluated, the variable named by
 ``<resultVar>`` must be manually removed from the cache.

Modules/CheckOBJCXXSourceCompiles.cmake

@@ -25,7 +25,7 @@ Check if given Objective-C++ source compiles and links into an executable.
   expressions.
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckOBJCXXSourceRuns.cmake

@@ -24,7 +24,7 @@ subsequently be run.
   false (e.g. an empty string or an error message).
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckSourceCompiles.cmake

@@ -48,7 +48,7 @@ Check if given source compiles and links into an executable.
     HAVE_ERROR_STOP)
 
   The check is only performed once, with the result cached in the variable
-  named by ``<resultVar>``. Every subsequent CMake run will re-use this cached
+  named by ``<resultVar>``. Every subsequent CMake run will reuse this cached
   value rather than performing the check again, even if the ``<code>`` changes.
   In order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/CheckSourceRuns.cmake

@@ -48,7 +48,7 @@ subsequently be run.
     HAVE_COARRAY)
 
   The check is only performed once, with the result cached in the variable named
-  by ``<resultVar>``. Every subsequent CMake run will re-use this cached value
+  by ``<resultVar>``. Every subsequent CMake run will reuse this cached value
   rather than performing the check again, even if the ``<code>`` changes. In
   order to force the check to be re-evaluated, the variable named by
   ``<resultVar>`` must be manually removed from the cache.

Modules/Compiler/GNU-CXX-FeatureTests.cmake

@@ -54,7 +54,7 @@ set(_cmake_feature_test_cxx_user_literals "${GNU47_CXX11}")
 # NOTE: C++11 was ratified in September 2011. GNU 4.7 is the first minor
 # release following that (March 2012), and the first minor release to
 # support -std=c++11. Prior to that, support for C++11 features is technically
-# experiemental and possibly incomplete (see for example the note below about
+# experimental and possibly incomplete (see for example the note below about
 # cxx_variadic_template_template_parameters)
 # GNU does not define __cplusplus correctly before version 4.7.
 # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=1773

Modules/Compiler/LCC-CXX-FeatureTests.cmake

@@ -54,7 +54,7 @@ set(_cmake_feature_test_cxx_user_literals "${GNU47_CXX11}")
 # NOTE: C++11 was ratified in September 2011. GNU 4.7 is the first minor
 # release following that (March 2012), and the first minor release to
 # support -std=c++11. Prior to that, support for C++11 features is technically
-# experiemental and possibly incomplete (see for example the note below about
+# experimental and possibly incomplete (see for example the note below about
 # cxx_variadic_template_template_parameters)
 # GNU does not define __cplusplus correctly before version 4.7.
 # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=1773

Modules/ExternalProject.cmake

@@ -522,7 +522,7 @@ overridden if required.
   use the same generator as the main project, but the ``CMAKE_GENERATOR``
   option can be given to override this.  The project is responsible for
   adding any toolchain details, flags or other settings it wants to
-  re-use from the main project or otherwise specify (see ``CMAKE_ARGS``,
+  reuse from the main project or otherwise specify (see ``CMAKE_ARGS``,
   ``CMAKE_CACHE_ARGS`` and ``CMAKE_CACHE_DEFAULT_ARGS`` below).
 
   For non-CMake external projects, the ``CONFIGURE_COMMAND`` option must
@@ -593,7 +593,7 @@ overridden if required.
   as initial defaults only and will not override any variables already set
   from a previous run. Use this option with care, as it can lead to
   different behavior depending on whether the build starts from a fresh
-  build directory or re-uses previous build contents.
+  build directory or reuses previous build contents.
 
   .. versionadded:: 3.15
     If the CMake generator is the ``Green Hills MULTI`` and not overridden,

Modules/FindCUDA.cmake

@@ -1423,7 +1423,7 @@ function(CUDA_COMPUTE_BUILD_PATH path build_path)
   # Only deal with CMake style paths from here on out
   file(TO_CMAKE_PATH "${path}" bpath)
   if (IS_ABSOLUTE "${bpath}")
-    # Absolute paths are generally unnessary, especially if something like
+    # Absolute paths are generally unnecessary, especially if something like
     # file(GLOB_RECURSE) is used to pick up the files.
 
     string(FIND "${bpath}" "${CMAKE_CURRENT_BINARY_DIR}" _binary_dir_pos)

Modules/FindEnvModules.cmake

@@ -81,7 +81,7 @@ modules:
 
 .. command:: env_module
 
-  Execute an aribitrary module command:
+  Execute an arbitrary module command:
 
   .. code-block:: cmake
 

Modules/FindMPI.cmake

@@ -436,7 +436,7 @@ function (_MPI_interrogate_compiler LANG)
   # a particular MPICH derivate might check compiler interoperability.
   # Intel MPI in particular does this with I_MPI_CHECK_COMPILER.
   file(TO_NATIVE_PATH "${CMAKE_${LANG}_COMPILER}" _MPI_UNDERLAYING_COMPILER)
-  # On Windows, the Intel MPI batch scripts can only work with filnames - Full paths will break them.
+  # On Windows, the Intel MPI batch scripts can only work with filenames - Full paths will break them.
   # Due to the lack of other MPICH-based wrappers for Visual C++, we may treat this as default.
   if(MSVC)
     get_filename_component(_MPI_UNDERLAYING_COMPILER "${_MPI_UNDERLAYING_COMPILER}" NAME)

Modules/FindSDL.cmake

@@ -181,7 +181,7 @@ if(SDL_LIBRARY_TEMP)
 
   # For OS X, SDL uses Cocoa as a backend so it must link to Cocoa.
   # CMake doesn't display the -framework Cocoa string in the UI even
-  # though it actually is there if I modify a pre-used variable.
+  # though it actually is there if I modify a preused variable.
   # I think it has something to do with the CACHE STRING.
   # So I use a temporary variable until the end so I can set the
   # "real" variable in one-shot.

Modules/FindSDL_sound.cmake

@@ -196,7 +196,7 @@ if(SDL_FOUND AND SDL_SOUND_INCLUDE_DIR AND SDL_SOUND_LIBRARY)
 
     # I expect that MPGLIB, VOC, WAV, AIFF, and SHN are compiled in statically.
     # I think Timidity is also compiled in statically.
-    # I've never had to explcitly link against Quicktime, so I'll skip that for now.
+    # I've never had to explicitly link against Quicktime, so I'll skip that for now.
 
     set(SDL_SOUND_LIBRARIES_TMP ${SDL_SOUND_LIBRARY})
 

Modules/FindXCTest.cmake

@@ -74,7 +74,7 @@ if(CMAKE_EFFECTIVE_SYSTEM_NAME STREQUAL "Apple"
   # platform directory which is not added to the CMAKE_FIND_ROOT_PATH
   # (only to CMAKE_SYSTEM_FRAMEWORK_PATH) and therefore not searched.
   #
-  # Until this is properly addressed, temporaily add the platform
+  # Until this is properly addressed, temporarily add the platform
   # directory to CMAKE_FIND_ROOT_PATH.
   list(APPEND CMAKE_FIND_ROOT_PATH "${_CMAKE_OSX_SYSROOT_PATH}/../..")
 endif()

Modules/Internal/CPack/CPackFreeBSD.cmake

@@ -66,7 +66,7 @@ _cpack_freebsd_fallback_var("CPACK_FREEBSD_PACKAGE_DESCRIPTION"
     )
 
 # There's really only one homepage for a project, so
-# re-use the Debian setting if it's there.
+# reuse the Debian setting if it's there.
 _cpack_freebsd_fallback_var("CPACK_FREEBSD_PACKAGE_WWW"
     "CPACK_PACKAGE_HOMEPAGE_URL"
     "CPACK_DEBIAN_PACKAGE_HOMEPAGE"

Modules/UseJava.cmake

@@ -1521,7 +1521,7 @@ function (create_javah)
       "CLASSES;CLASSPATH;DEPENDS"
       ${ARGN})
 
-    # ckeck parameters
+    # check parameters
     if (NOT _create_javah_TARGET AND NOT _create_javah_GENERATED_FILES)
       message (FATAL_ERROR "create_javah: TARGET or GENERATED_FILES must be specified.")
     endif()