Telcon: 2022 04 27
Tamara Dahlgren edited this page Apr 27, 2022
·
27 revisions
- Peter Scheibel (host)
- Mark Krentel
- Massimiliano Culpo
- Matt Belhorn
- Mitchell Dorrel
- Phil Regier
- Tammy Dahlgren
- Wileam Phan
-
(Phil) State of container-ization/environments
- If we package spack with OpenSUSE and advertise it to users for creating containers, then it uses Ubuntu
- You can edit a YAML file to have them generate containers for other distros
- But ideally you wouldn't have to
- (Massimiliano) there are many configuration options, so it would potentially be involved to expose them as command-line options
- Side note: where is documentation for how to update
spack.yaml
to choose an alternative distribution - See also: https://spack.readthedocs.io/en/latest/containers.html#configuration-reference
-
Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-20: reuse and missing package.py files
- See also: https://github.com/spack/spack/pull/30092
- "This commit discard specs from unknown namespaces from the ones that can be "reused" during concretization. Previously Spack would just error out when encountering them."
- Note this should address an entire missing repos as well as a single missing package in a repo
- See also: https://github.com/spack/spack/pull/30092
-
(Wileam)
spack update
: https://github.com/spack/spack/issues/9134 -
(Wileam) https://github.com/spack/spack/issues/30134
- Executable script is git-cloned, but loses execute permissions
-
(Wileam) aarch64 target
- (Massimiliano) See: https://github.com/archspec/archspec-json/issues/42
-
(Mitchell) can we customize flags for a given target?
- The JSON file in archspec lists flags for each target
- Spack vendors archspec in
lib/spack/external
, you can modify the file there - (Matt) You can also define a custom compiler like
gcc@custom-version
with additional flags
-
(Mitchell) when is compilers-as-dependencies going to happen?
- After 0.18
-
(Matt) support for mixed-toolchain
- loosely-supported now
- (Peter) Can also use
spack-python
to possibly propagate these in a more controlled manner
- Upcoming Cray support changes:
- For 0.18
- manifest (https://github.com/spack/spack/pull/29652)
- (Greg) module list cray environments
- (Matt) if we build an environment, and one package fails, then module files are not generated
- Want
spack module refresh
but only to generate module files that haven't been generated yet
- Want
- Updating compiler wrapper to strip
-Werror
(optionally): https://github.com/spack/spack/pull/30284 - (Wileam) Adding fpm as a build system
- Default action for concretization in environments: https://github.com/spack/spack/pull/29942#issuecomment-1097287194
- Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-06:
warning()
directive - (Wileam) Can't bootstrap
llvm@13
and@14
if gold is enabled (which is the default behavior) https://github.com/spack/spack/issues/29350 - How to reorganize the docs?
- Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-03-09: Packages with multiple build systems
- https://github.com/spack/spack/pull/29530
- (Peter) What about external package repositories?
- Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-13:
not
in spec syntax