zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

typo fixes from Adam

Browse Source
This commit is contained in:
Todd Gamblin 2014-01-14 23:50:50 -08:00
parent f1188e3664
commit cab94f86ee
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
lib/spack/docs/basic_usage.rst
View File

@ -234,7 +234,7 @@ completely remove the directory in which the package was installed.
spack uninstall mpich spack uninstall mpich
If there are other installed packages depend on the package to be If there are still installed packages that depend on the package to be
uninstalled, spack will issue a warning. In general, it is safer to uninstalled, spack will issue a warning. In general, it is safer to
remove dependent packages *before* removing their dependencies. Not remove dependent packages *before* removing their dependencies. Not
doing so risks breaking packages on your system. To remove a package doing so risks breaking packages on your system. To remove a package
@ -269,7 +269,7 @@ Here is an example of a much longer spec than we've seen thus far::
mpileaks @1.2:1.4 %gcc@4.7.5 +debug -qt =bgqos_0 ^callpath @1.1 %gcc@4.7.2 mpileaks @1.2:1.4 %gcc@4.7.5 +debug -qt =bgqos_0 ^callpath @1.1 %gcc@4.7.2
If provided to ``spack install``, this will install the ``mpileaks`` If provided to ``spack install``, this will install the ``mpileaks``
library at some version between ``1.2`` and ``1.4`` (inclusive),, library at some version between ``1.2`` and ``1.4`` (inclusive),
built using ``gcc`` at version 4.7.5 for the Blue Gene/Q architecture, built using ``gcc`` at version 4.7.5 for the Blue Gene/Q architecture,
with debug options enabled, and without Qt support. Additionally, it with debug options enabled, and without Qt support. Additionally, it
says to link it with the ``callpath`` library (which it depends on), says to link it with the ``callpath`` library (which it depends on),
@ -543,12 +543,12 @@ a particular ``mpich`` version::
spack install mpileaks ^mpich@3 spack install mpileaks ^mpich@3
In this case, ``mpileaks`` only needs MPI-1 commands, so any MPI The ``mpileaks`` package in particular only needs MPI-1 commands, so
implementation will do. If another package depends on ``mpi@2`` and any MPI implementation will do. If another package depends on
you try to give it an insufficient MPI implementation (e.g., one that ``mpi@2`` and you try to give it an insufficient MPI implementation
provides only ``mpi@:1``), then Spack will raise an error. Likewise, (e.g., one that provides only ``mpi@:1``), then Spack will raise an
if you try to plug in some package that doesn't provide MPI, Spack error. Likewise, if you try to plug in some package that doesn't
will raise an error. provide MPI, Spack will raise an error.
``spack providers`` ``spack providers``
~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~

2
lib/spack/docs/getting_started.rst
View File

@ -18,7 +18,7 @@ to go:
.. code-block:: sh .. code-block:: sh
$ export PATH=spack/bin:$SPACK_HOME $ export PATH=spack/bin:$PATH
$ spack install libelf $ spack install libelf
In general, most of your interactions with Spack will be through the In general, most of your interactions with Spack will be through the