Telcon: 2022 08 31
Peter Scheibel edited this page Aug 31, 2022
·
13 revisions
(held August 31st 2022)
- Peter Scheibel (host)
- Srinath Vadlamani
- Davide DelVento
- Richarda Butler
- Massimiliano Culpo
- Phil Regier
- Tammy Dahlgren
- (Srinath) current or future considerations for profiling tools like perftools https://www.olcf.ornl.gov/software_package/perftools/
Driver unwrapping
- Cray PE:
CC
are wrappers - can also be considered drivers: if you load perftools, this changes
CC
behavior - How does Spack address this?
- For now, you could have different compiler definitions (i.e. separate entries in compilers.yaml) for with-perftools and without-perftools
- can you enable perftools via flag?
- No: only through module loading
- (Peter) could we make our own wrapper though that treats that like a flag?
- Cray PE:
- (Srinath) is the order of modules listed in a compilers.yaml entry followed when spack initializes a compiler
- (Srinath) desire for command to say the location of the environment view
spack location -v
- or
spack env view --show
- (Massimiliano) multiple build systems
- (Davide) Desire to duplicate an installation
- Does overwrite of
spack.lock
/spack.yaml
work? - You can also "version" the environment: copy the lock/yaml to a new environment in the production environment (then, if users have no issues with the new environment, remove the old environment)
- If the user exposes the packages in the environment with modules, do we need per-environment modules?
- (Davide) In my case I version-control the modules so this isn't an issue
- Does overwrite of
- (Davide) what about major version updates?
- Do users pull major updates to their installations? How big a leap do people do in general? And how often?
- (Peter) we may have a poll on this, but otherwise it would be interesting to conduct one
- (Chris) Options for
spack style
checking of user package repos (see https://github.com/spack/spack/pull/31938). - (Brian) Sanitizing repo, getting rid of improperly-concretized packages (i.e. how do I get rid of old stuff I don't use now)
- (in particular reuse)
- (Mark) Ping on #27247
- (Matt) Package reuse is nice, but how can we refresh a single package?
- E.g. want to use the newest version of
spectrum-mpi
- E.g. want to use the newest version of
- (Matt) How does
spack deprecate
handle refreshing module files for packages that depend on a deprecated spec in an lmod hierarchy?- e.g. if you deprecate the old MPI, does the lmod refresh use the newer MPI in the hierarchy
- (Massimiliano) Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-06-08: multiple build systems used by one package
- (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
- Issue on
fpm
repo: https://github.com/fortran-lang/fpm/issues/79
- Issue on
- 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 externals detection be expanded from executables only to arbitrary files (e.g. header or
.a
/.so
library files)?- For
llvm@13
and@14
with+gold
, see issue comment and PR https://github.com/spack/spack/pull/30954 - BLAS detection is also affected, see https://spackpm.slack.com/archives/C5W7NKZJT/p1659734369147249
- For
- Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-13:
not
in spec syntax - (Phil) Issues with SSL signature authentication at SNL, see https://spackpm.slack.com/archives/G7XED8NAD/p1660009273764719