@@ -156,7 +156,7 @@ one does
156156module load MPI_D
157157```
158158
159- thent MPI_C gets unloaded, Lmod notices that it also has to unload/deactivate Appl_E, then will load MPI_D for Compiler_A and
159+ then MPI_C gets unloaded, Lmod notices that it also has to unload/deactivate Appl_E, then will load MPI_D for Compiler_A and
160160finally will notice that there is an equivalent Appl_E module available again, and Lmod will load that one also. However,
161161now loading Compiler_B will cause a warning that MPI_D and Appl_E have been deactivated as there is no module name MPI_D in
162162any version for Compiler_B.
@@ -416,31 +416,31 @@ search for those too.
416416 This tells that there is no ` ` CMake` ` module on the system but that two versions
417417 of ` ` CMake` ` are provided in another module.
418418
419- 3. ` module spider < extension name> /< version> ` will show more information on the
420- extension, including which module provides the extension and which other modules
421- have to be loaded to make that module available. E.g., on LUMI,
422- ` ` `
423- module spider CMake/3.22.2
424- ` ` `
425- will output something along the lines of
426- ` ` `
427- -----------------------------------------------------------------------
428- CMake: CMake/3.22.2 (E)
429- -----------------------------------------------------------------------
430- This extension is provided by the following modules. To access the
431- extension you must load one of the following modules. Note that any
432- module names in parentheses show the module location in the software
433- hierarchy.
434-
435- buildtools/21.12 (LUMI/21.12 partition/L)
436- buildtools/21.12 (LUMI/21.12 partition/G)
437- buildtools/21.12 (LUMI/21.12 partition/D)
438- buildtools/21.12 (LUMI/21.12 partition/C)
439- buildtools/21.12 (CrayEnv)
419+ 3. ` ` module spider <extension name>/<version>` ` will show more information on the
420+ extension, including which module provides the extension and which other modules
421+ have to be loaded to make that module available. E.g., on LUMI,
422+ ` ` `
423+ module spider CMake/3.22.2
440424 ` ` `
441- (output abbreviated and slightly reformatted for readability). This tells that
442- ` ` CMake/3.22.2` ` is provided by the ` ` bvuildtools/21.12` ` module and that there
443- are 5 different ways to make that package available.
425+ will output something along the lines of
426+ ` ` `
427+ -----------------------------------------------------------------------
428+ CMake: CMake/3.22.2 (E)
429+ -----------------------------------------------------------------------
430+ This extension is provided by the following modules. To access the
431+ extension you must load one of the following modules. Note that any
432+ module names in parentheses show the module location in the software
433+ hierarchy.
434+
435+ buildtools/21.12 (LUMI/21.12 partition/L)
436+ buildtools/21.12 (LUMI/21.12 partition/G)
437+ buildtools/21.12 (LUMI/21.12 partition/D)
438+ buildtools/21.12 (LUMI/21.12 partition/C)
439+ buildtools/21.12 (CrayEnv)
440+ ` ` `
441+ (output abbreviated and slightly reformatted for readability). This tells that
442+ ` ` CMake/3.22.2` ` is provided by the ` ` bvuildtools/21.12` ` module and that there
443+ are 5 different ways to make that package available.
444444
445445??? Bug " Restrictions with older Lmod versions"
446446 At the time of development of this tutorial, Cray is still using the pretty old
@@ -787,7 +787,7 @@ still fail to remove the 2.7 directory from ``PYTHONPATH``.
787787 the module as deactivated but not as unloaded.
788788
789789 Lmod proceeds with loading the ` ` MyPython/3.6.10` ` module. This will now set
790- ` ` PTHON_API_VERSION ` ` to ` ` 3.6` ` and add a directory with name ending on
790+ ` ` PYTHON_API_VERSION ` ` to ` ` 3.6` ` and add a directory with name ending on
791791 ` ` level2/PythonAPI/3.6` ` to ` ` MODULEPATH` ` .
792792
793793 Things are not done yet though. As the ` ` MODULEPATH` ` has changed, Lmod looks at its list
0 commit comments