Installing packages via a Spack-built GCC

[Erik Schnetter]

I recently mentioned using a Spack-built GCC to install Spack packages.

The script below does just this for a variety of packages. This is
approximately the list of packages I need on various HPC systems.
Although this looks like a script, I typically execute the lines
manually to catch errors.

-erik

--
Erik Schnetter <schn...@gmail.com>
http://www.perimeterinstitute.ca/personal/eschnetter/

[Gamblin, Todd]

Thanks ‹ this is helpful as an example workflow and maybe as something we
could look at to improe the command line to make installing stacks like
this easier.

On 2/23/16, 11:17 AM, "sp...@googlegroups.com on behalf of Erik Schnetter"

<sp...@googlegroups.com on behalf of schn...@gmail.com> wrote:

>I recently mentioned using a Spack-built GCC to install Spack packages.
>
>The script below does just this for a variety of packages. This is
>approximately the list of packages I need on various HPC systems.
>Although this looks like a script, I typically execute the lines
>manually to catch errors.
>
>-erik
>
>--
>Erik Schnetter <schn...@gmail.com>

>http://secure-web.cisco.com/1vh3VYIOmFE_6ADQi7PUulWNr-gBjj8i-yInZknd1-Jef2
>k4fIt7w0I1X6VAH4IMlEZlp8fasVx-fN_3MblknRHxznbTwnPQud33uiszMdFPMlh75OW5fFq2
>6_sa3NxX13TYB7XlD6jmKQelZkaP5vJvPzhp_FAJ1Vm6mZ1risPLl-JrOWvL1ULAGO5gWJtT7S
>0mUAy8COfY-c6yNsCuHm9PLyr0ETtzxCjgIK2kqUnzvCI88ej0tp69xrGwtUjHJJXppAUezYBw
>u4qh7fcivnGvUAxjki3theCMAs0c54AKUjlRUIHngSzNhBEnjk4u3ZvCT6J4le27mYIGS0wRPu
>lWHaG-rwNo8j9rglyRM4kI/http%3A%2F%2Fwww.perimeterinstitute.ca%2Fpersonal%2
>Feschnetter%2F
>
>--
>You received this message because you are subscribed to the Google Groups
>"Spack" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to spack+un...@googlegroups.com.
>To post to this group, send email to sp...@googlegroups.com.
>Visit this group at
>https://secure-web.cisco.com/1N5yZMdIKRu1DECch5RCi-FT8XEEew3JlA5hAPyIX1-ke
>yKpcQWR-PVeV3wxJHsbgzEeRjLdXrrnwnnKn17PrU34uGi6u3g1TAOJn561q9p65r6TuTgnrNK
>cR0i2lkhDI87JSL_9gqqjCJdoEjfS6aj_ipCTN_wJS-OCLobKtDWSpoNL9qHPzrKfqMZffIvFZ
>BiUHnZhH8mMUsmuoZqvBkEYGRGNvQRvkclJ5ZgeP59UAIKhTlLcNnEZNLXgXCKxWnDFIDm_SVj
>jd_VgwqAucm6E68ag1pr5IYsKfCtXND7Ym1h1p36C0nD3F6DRUuqQpF3mjhKn5shLFPXL6OTyC
>VEMBwG0jvphgqAlazKEb_fjnyAj-WcoNXp0hMK2kynxe/https%3A%2F%2Fgroups.google.c
>om%2Fgroup%2Fspack.
>For more options, visit
>https://secure-web.cisco.com/1sR0ScWCf5BP8V9LoS2_UTi9AVkVhNacT4YbC2T1wjhQr
>jFs-MynejLYt3NtxR0ozRE_dmxiqnkvufVZp4VMr9lzKWreGTAnDlOkE1haMKfrsQqQl-2oELZ
>OKXw1hrjBMj40dFOE8RT582mRLTMKiKzqcLGX9qPETY7l0WcSc-G49PGb0rIdAuHGvhe8l5llD
>PBViPtR2PvtET0AoFaP925PLzxXprs5I12uIaVujd6-1JrSy-3c4WbqYVJ7tpPfANHe2DO0CJ-
>hgpVIDHAQI9xVMtIcytGEv_dX4Vn-HKWXpxsUPXXm2A-xPQQ87NEwPhMlpWI1H3EDQm02s2FIP
>SAoz3Q9KS3VrzZ_BiMUhhx73Cd448Gbj9AxuNjggtBL_/https%3A%2F%2Fgroups.google.c
>om%2Fd%2Foptout.

[Gamblin, Todd]

What’s the rationale behind using the -spack suffix for the gcc 5.3.0
compiler? Why not just do this:

spack install g...@5.3.0
spack compiler add $(spack location -i g...@5.3.0)

Then install everything with %g...@5.3.0? Does this not work?

-Todd



On 2/23/16, 11:19 AM, "sp...@googlegroups.com on behalf of Gamblin, Todd"

<sp...@googlegroups.com on behalf of gamb...@llnl.gov> wrote:

>Thanks ‹ this is helpful as an example workflow and maybe as something we
>could look at to improe the command line to make installing stacks like
>this easier.
>
>On 2/23/16, 11:17 AM, "sp...@googlegroups.com on behalf of Erik Schnetter"
><sp...@googlegroups.com on behalf of schn...@gmail.com> wrote:
>
>>I recently mentioned using a Spack-built GCC to install Spack packages.
>>
>>The script below does just this for a variety of packages. This is
>>approximately the list of packages I need on various HPC systems.
>>Although this looks like a script, I typically execute the lines
>>manually to catch errors.
>>
>>-erik
>>
>>--
>>Erik Schnetter <schn...@gmail.com>
>>http://secure-web.cisco.com/1vh3VYIOmFE_6ADQi7PUulWNr-gBjj8i-yInZknd1-Jef
>>2
>>k4fIt7w0I1X6VAH4IMlEZlp8fasVx-fN_3MblknRHxznbTwnPQud33uiszMdFPMlh75OW5fFq
>>2
>>6_sa3NxX13TYB7XlD6jmKQelZkaP5vJvPzhp_FAJ1Vm6mZ1risPLl-JrOWvL1ULAGO5gWJtT7
>>S
>>0mUAy8COfY-c6yNsCuHm9PLyr0ETtzxCjgIK2kqUnzvCI88ej0tp69xrGwtUjHJJXppAUezYB
>>w
>>u4qh7fcivnGvUAxjki3theCMAs0c54AKUjlRUIHngSzNhBEnjk4u3ZvCT6J4le27mYIGS0wRP
>>u

>>lWHaG-rwNo8j9rglyRM4kI/http%3A%2F%2Fhttp://secure-web.cisco.com/1c1rfKyjb
>>bzuINOjDUDzGiUna4yIU8ShuYptoBLrQMKYXIFaZjYwQpvYe3kBCRDgV_6mjJM-Cd9LHSPh0M
>>b9mSnmdN1NoeMYpdXTi9wUfhUAQzEULHe1wOreJANOCxLjGSFV4x3qvwUOMebszPspePZuJNj
>>nFKsVI7EGGf9koRFU40aCcdXcofFGPgGOh_onVj9eCR65KXcMnuio1-h8LNc3hnGB3T_hotir
>>S8hBItqcrHRSih1IxyHzF11eDS3iNQoc1PBMN2GxJPKmwkmakHo896zWNYNTRIcBZc4cXtquP
>>y4AmR1GRUHhHcxxeQrqpKeuvJaBA0EXzonM_IQIaozm1bJk-krNzXDfAZdZ_Lqk/http%3A%2

>https://secure-web.cisco.com/1U0_wBUi8586EGqb7d2uJMh9hyH6kEdBoScwpTgYvL-jR
>q7VQIl2Cuh5rQPWn-FY2ILkOlUjk4wJVfuDYpFAv7N5NPrWp4P-V0M85pIzfqfj4-FaStsCCRo
>xfvPbDZkekwa3qLlQ0-uXpyw6emFJGJSlsFoXhE7Y-AYg9ryXTm5s9IX8g5qvN7jew7J2ltco1
>h6ZtSRlvDmx5nXRFJBlwT-E4NaLR-TjchMWU49wECyRp9XkagrJkvNwkgyVRFgjeFjZx3iXaMS
>aU5QMVNo_H6YRZo5EqB-BTR_G9K7CVKPIoYcW1cXn0CIvcJfKNAwdtq9tlwYMTd_0K9oumI8s0
>QgPbEcLwIPgTZFb77bWcH0jRAhBG7q_egXLc9qxmsUAv/https%3A%2F%2Fgroups.google.c

>om%2Fgroup%2Fspack.
>For more options, visit

>https://secure-web.cisco.com/1bwcbHDxQE36rrR5CwI_L1qEdgbJTIhpd_aV1AhfUgvAa
>Sp6b6F3nt9nUzvY7yQBDywimAVIVQgQGYBEriEPf55txnXNQ71FJX6B2AqcRJffw1zU-na_IYT
>6U9AoKHll7nqrIq52tBZkHBtfPLuxhK9fPdSYmzf63pKaZAL4NtVNntcKJ7IbDSkjncYi_8zVZ
>0HarSZlPrwBSz15obZj2XcWpueZEdhVWS6AOT9Ug8jb6bi97UfqSV9qHWd2jxRVuhyY0aJ0BgP
>Z0eV_GJo9dVEMApTi-HpWJKflAjPq4o6r1DgxGrsPRllHiSbpoOcHAytEAjl7gplB-kzNOCr78
>zXdC8Avxso4IPOojzfKXOEujNuBtVuCyVxy4X6iw6XFK/https%3A%2F%2Fgroups.google.c
>om%2Fd%2Foptout.
>

[Erik Schnetter]

Todd

This does not work if there is already a compiler on the system that
is identified as "g...@5.3.0". Thus we need to invent a new, unique
name.

An alternative would be to remove this compiler from the list of known
compilers. That is only possible if there is then at least one other
compiler left that we can use to build gcc...

-erik

http://www.perimeterinstitute.ca/personal/eschnetter/