diff options
| author | Xavier Delaruelle <xavier.delaruelle@cea.fr> | 2023-03-19 02:42:50 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-19 01:42:50 +0000 |
| commit | df97827a7b9e7feafd6c7435f947925c6062068a (patch) | |
| tree | afc82346866295c57dec4064db8b0a4d6fa0fd64 /lib/spack/docs/build_systems | |
| parent | 4ffdde94efd70e03be685b8addad8fd60907fe0a (diff) | |
| download | spack-df97827a7b9e7feafd6c7435f947925c6062068a.tar.gz spack-df97827a7b9e7feafd6c7435f947925c6062068a.tar.bz2 spack-df97827a7b9e7feafd6c7435f947925c6062068a.tar.xz spack-df97827a7b9e7feafd6c7435f947925c6062068a.zip | |
Fix case spelling for Lmod and Tcl (#36215)
Diffstat (limited to 'lib/spack/docs/build_systems')
| -rw-r--r-- | lib/spack/docs/build_systems/inteloneapipackage.rst | 2 | ||||
| -rw-r--r-- | lib/spack/docs/build_systems/intelpackage.rst | 4 | ||||
| -rw-r--r-- | lib/spack/docs/build_systems/pythonpackage.rst | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/lib/spack/docs/build_systems/inteloneapipackage.rst b/lib/spack/docs/build_systems/inteloneapipackage.rst index 6cc0b33192..410294c1b0 100644 --- a/lib/spack/docs/build_systems/inteloneapipackage.rst +++ b/lib/spack/docs/build_systems/inteloneapipackage.rst @@ -124,7 +124,7 @@ Using oneAPI Tools Installed by Spack ===================================== Spack can be a convenient way to install and configure compilers and -libaries, even if you do not intend to build a Spack package. If you +libraries, even if you do not intend to build a Spack package. If you want to build a Makefile project using Spack-installed oneAPI compilers, then use spack to configure your environment:: diff --git a/lib/spack/docs/build_systems/intelpackage.rst b/lib/spack/docs/build_systems/intelpackage.rst index f565f205ef..d64fd46971 100644 --- a/lib/spack/docs/build_systems/intelpackage.rst +++ b/lib/spack/docs/build_systems/intelpackage.rst @@ -397,7 +397,7 @@ for specifics and examples for ``packages.yaml`` files. .. If your system administrator did not provide modules for pre-installed Intel tools, you could do well to ask for them, because installing multiple copies - of the Intel tools, as is wont to happen once Spack is in the picture, is + of the Intel tools, as is won't to happen once Spack is in the picture, is bound to stretch disk space and patience thin. If you *are* the system administrator and are still new to modules, then perhaps it's best to follow the `next section <Installing Intel tools within Spack_>`_ and install the tools @@ -653,7 +653,7 @@ follow `the next section <intel-install-libs_>`_ instead. * If you specified a custom variant (for example ``+vtune``) you may want to add this as your preferred variant in the packages configuration for the ``intel-parallel-studio`` package as described in :ref:`package-preferences`. Otherwise you will have to specify - the variant everytime ``intel-parallel-studio`` is being used as ``mkl``, ``fftw`` or ``mpi`` + the variant every time ``intel-parallel-studio`` is being used as ``mkl``, ``fftw`` or ``mpi`` implementation to avoid pulling in a different variant. * To set the Intel compilers for default use in Spack, instead of the usual ``%gcc``, diff --git a/lib/spack/docs/build_systems/pythonpackage.rst b/lib/spack/docs/build_systems/pythonpackage.rst index 807af44ed9..17295a457f 100644 --- a/lib/spack/docs/build_systems/pythonpackage.rst +++ b/lib/spack/docs/build_systems/pythonpackage.rst @@ -582,7 +582,7 @@ libraries. Make sure not to add modules/packages containing the word "test", as these likely won't end up in the installation directory, or may require test dependencies like pytest to be installed. -Instead of defining the ``import_modules`` explicity, only the subset +Instead of defining the ``import_modules`` explicitly, only the subset of module names to be skipped can be defined by using ``skip_modules``. If a defined module has submodules, they are skipped as well, e.g., in case the ``plotting`` modules should be excluded from the |