summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdam J. Stewart <ajstewart426@gmail.com>2019-10-03 10:31:32 -0500
committerGitHub <noreply@github.com>2019-10-03 10:31:32 -0500
commit24f8d1042bfb6b3abe33816903d45667b44f3926 (patch)
treecc9820d0ae3af8eb5c294419e146a592911b18fa
parentdac34147c017e35043f93c2be2959377b5a9a50e (diff)
downloadspack-24f8d1042bfb6b3abe33816903d45667b44f3926.tar.gz
spack-24f8d1042bfb6b3abe33816903d45667b44f3926.tar.bz2
spack-24f8d1042bfb6b3abe33816903d45667b44f3926.tar.xz
spack-24f8d1042bfb6b3abe33816903d45667b44f3926.zip
Update compilers.yaml location in Getting Started docs (#13029)
-rw-r--r--lib/spack/docs/getting_started.rst25
1 files changed, 14 insertions, 11 deletions
diff --git a/lib/spack/docs/getting_started.rst b/lib/spack/docs/getting_started.rst
index eeeffcc25f..b7ba386bb2 100644
--- a/lib/spack/docs/getting_started.rst
+++ b/lib/spack/docs/getting_started.rst
@@ -190,7 +190,7 @@ where the compiler is installed. For example:
.. code-block:: console
$ spack compiler find /usr/local/tools/ic-13.0.079
- ==> Added 1 new compiler to ~/.spack/compilers.yaml
+ ==> Added 1 new compiler to ~/.spack/linux/compilers.yaml
intel@13.0.079
Or you can run ``spack compiler find`` with no arguments to force
@@ -202,7 +202,7 @@ installed, but you know that new compilers have been added to your
$ module load gcc-4.9.0
$ spack compiler find
- ==> Added 1 new compiler to ~/.spack/compilers.yaml
+ ==> Added 1 new compiler to ~/.spack/linux/compilers.yaml
gcc@4.9.0
This loads the environment module for gcc-4.9.0 to add it to
@@ -247,7 +247,7 @@ Manual compiler configuration
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If auto-detection fails, you can manually configure a compiler by
-editing your ``~/.spack/compilers.yaml`` file. You can do this by running
+editing your ``~/.spack/<platform>/compilers.yaml`` file. You can do this by running
``spack config edit compilers``, which will open the file in your ``$EDITOR``.
Each compiler configuration in the file looks like this:
@@ -263,7 +263,7 @@ Each compiler configuration in the file looks like this:
cxx: /usr/local/bin/icpc-15.0.024-beta
f77: /usr/local/bin/ifort-15.0.024-beta
fc: /usr/local/bin/ifort-15.0.024-beta
- spec: intel@15.0.0:
+ spec: intel@15.0.0
For compilers that do not support Fortran (like ``clang``), put
``None`` for ``f77`` and ``fc``:
@@ -469,18 +469,21 @@ Fortran.
install GCC with Spack (``spack install gcc``) or with Homebrew
(``brew install gcc``).
-#. The only thing left to do is to edit ``~/.spack/compilers.yaml`` to provide
+#. The only thing left to do is to edit ``~/.spack/darwin/compilers.yaml`` to provide
the path to ``gfortran``:
.. code-block:: yaml
compilers:
- darwin-x86_64:
- clang@7.3.0-apple:
- cc: /usr/bin/clang
- cxx: /usr/bin/clang++
- f77: /path/to/bin/gfortran
- fc: /path/to/bin/gfortran
+ - compiler:
+ ...
+ paths:
+ cc: /usr/bin/clang
+ cxx: /usr/bin/clang++
+ f77: /path/to/bin/gfortran
+ fc: /path/to/bin/gfortran
+ spec: clang@11.0.0-apple
+
If you used Spack to install GCC, you can get the installation prefix by
``spack location -i gcc`` (this will only work if you have a single version