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

Update compilers.yaml location in Getting Started docs (#13029)

Browse Source
This commit is contained in:
Adam J. Stewart 2019-10-03 10:31:32 -05:00 committed by GitHub
parent dac34147c0
commit 24f8d1042b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -190,7 +190,7 @@ where the compiler is installed. For example:
.. code-block:: console .. code-block:: console
$ spack compiler find /usr/local/tools/ic-13.0.079 $ 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 intel@13.0.079
Or you can run ``spack compiler find`` with no arguments to force 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 $ module load gcc-4.9.0
$ spack compiler find $ spack compiler find
==> Added 1 new compiler to ~/.spack/compilers.yaml ==> Added 1 new compiler to ~/.spack/linux/compilers.yaml
gcc@4.9.0 gcc@4.9.0
This loads the environment module for gcc-4.9.0 to add it to 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 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``. ``spack config edit compilers``, which will open the file in your ``$EDITOR``.
Each compiler configuration in the file looks like this: 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 cxx: /usr/local/bin/icpc-15.0.024-beta
f77: /usr/local/bin/ifort-15.0.024-beta f77: /usr/local/bin/ifort-15.0.024-beta
fc: /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 For compilers that do not support Fortran (like ``clang``), put
``None`` for ``f77`` and ``fc``: ``None`` for ``f77`` and ``fc``:
@ -469,18 +469,21 @@ Fortran.
install GCC with Spack (``spack install gcc``) or with Homebrew install GCC with Spack (``spack install gcc``) or with Homebrew
(``brew install gcc``). (``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``: the path to ``gfortran``:
.. code-block:: yaml .. code-block:: yaml
compilers: compilers:
darwin-x86_64: - compiler:
clang@7.3.0-apple: ...
cc: /usr/bin/clang paths:
cxx: /usr/bin/clang++ cc: /usr/bin/clang
f77: /path/to/bin/gfortran cxx: /usr/bin/clang++
fc: /path/to/bin/gfortran 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 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 ``spack location -i gcc`` (this will only work if you have a single version