-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Description
In the first part of the tutorial, the example of spack install gmake
is shown, with the following output:
==> Compilers have been configured automatically from PATH inspection
[+] /usr (external gcc-11.4.0-j7ykyvm5ancnn5rt7f35ggs6hwoslo42)
[+] /usr (external glibc-2.35-epwvtixhoxdeufu6kbbrpaigv2p6iav4)
==> No binary for compiler-wrapper-1.0-rwnqblirwn5aenlmsbvsieo7mzw672ee found: installing from source
==> Installing compiler-wrapper-1.0-rwnqblirwn5aenlmsbvsieo7mzw672ee [3/5]
[....]
==> No binary for gcc-runtime-11.4.0-3c5xh7dqudxmyorlsrsfmjyggqk57vnr found: installing from source
==> Installing gcc-runtime-11.4.0-3c5xh7dqudxmyorlsrsfmjyggqk57vnr [4/5]
[....]
==> No binary for gmake-4.4.1-5vb6e4beeoff4jan2t7edfjyi3hf3p7g found: installing from source
==> Installing gmake-4.4.1-5vb6e4beeoff4jan2t7edfjyi3hf3p7g [5/5]
[....]
and then, it is said that;
You will see Spack installed gmake
, gcc
, gcc-runtime
, and glibc
. The glibc
and gcc-runtime
packages are automatically tracked by Spack to manage consistency requirements among compiler runtimes.
Whereas my understanding is that;
You will see Spack installed compiler-wrapper,
gcc-runtime
and gmake
. The glibc
and gcc
packages are automatically tracked by Spack to manage consistency requirements among compiler runtimes.
Let me know if i'm wrong. Thanks for building amazing software and tutorials
Cheers
Rémi
Metadata
Metadata
Assignees
Labels
No labels