diff options
| author | Todd Gamblin <tgamblin@llnl.gov> | 2014-01-14 23:50:50 -0800 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2014-01-14 23:50:50 -0800 |
| commit | cab94f86ee3ca62daf9a5b1cbfe5719c1f4fce65 (patch) | |
| tree | 078a014e8323e7c9c2680125eb38179f4577acbd /lib | |
| parent | f1188e36641e465c11f026ebfe521e006bb0a3d8 (diff) | |
| download | spack-cab94f86ee3ca62daf9a5b1cbfe5719c1f4fce65.tar.gz spack-cab94f86ee3ca62daf9a5b1cbfe5719c1f4fce65.tar.bz2 spack-cab94f86ee3ca62daf9a5b1cbfe5719c1f4fce65.tar.xz spack-cab94f86ee3ca62daf9a5b1cbfe5719c1f4fce65.zip | |
typo fixes from Adam
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/spack/docs/basic_usage.rst | 16 | ||||
| -rw-r--r-- | lib/spack/docs/getting_started.rst | 2 |
2 files changed, 9 insertions, 9 deletions
diff --git a/lib/spack/docs/basic_usage.rst b/lib/spack/docs/basic_usage.rst index 4c527d91d2..47dc754077 100644 --- a/lib/spack/docs/basic_usage.rst +++ b/lib/spack/docs/basic_usage.rst @@ -234,7 +234,7 @@ completely remove the directory in which the package was installed. 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 remove dependent packages *before* removing their dependencies. Not 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 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, with debug options enabled, and without Qt support. Additionally, it 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 -In this case, ``mpileaks`` only needs MPI-1 commands, so any MPI -implementation will do. If another package depends on ``mpi@2`` and -you try to give it an insufficient MPI implementation (e.g., one that -provides only ``mpi@:1``), then Spack will raise an error. Likewise, -if you try to plug in some package that doesn't provide MPI, Spack -will raise an error. +The ``mpileaks`` package in particular only needs MPI-1 commands, so +any MPI implementation will do. If another package depends on +``mpi@2`` and you try to give it an insufficient MPI implementation +(e.g., one that provides only ``mpi@:1``), then Spack will raise an +error. Likewise, if you try to plug in some package that doesn't +provide MPI, Spack will raise an error. ``spack providers`` ~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/lib/spack/docs/getting_started.rst b/lib/spack/docs/getting_started.rst index 5f495709c7..d5abd16f94 100644 --- a/lib/spack/docs/getting_started.rst +++ b/lib/spack/docs/getting_started.rst @@ -18,7 +18,7 @@ to go: .. code-block:: sh - $ export PATH=spack/bin:$SPACK_HOME + $ export PATH=spack/bin:$PATH $ spack install libelf In general, most of your interactions with Spack will be through the |