Skip to content
Peter Scheibel edited this page Nov 8, 2023 · 18 revisions

Wednesday November 8th, 9am PT (UTC -8:00)

Attendees

  • Peter Scheibel (host)
  • Tammy Dahlgren
  • Davide DelVento
  • Mark Krentel
  • Yang Liu
  • Prithvi Thakur
  • Brian Kyle
  • Kevin Fotso
  • Sreeram Venkat
  • Brian Van Essen
  • Cameron Smith RPI

Agenda

This meeting is for Q&A: there are no pre-planned general topics.

  • Davide: installed Julia with Spack
    • Extendable packages, some require pre-compilation
    • The default precompilation directory is based on where it was built
    • Users installing extensions with Julia are automatically using this directory
      • (Side note, this directory is based on the username and in /tmp/, but the directory is removed after installation, which allows another user to create a dir with the original name but owned by then)
    • Ideally all users could have a different path they do builds in
      • (so changing the path at build time would not be useful)
  • Yang: want to make external package module the default
    • Had preferences for ncurses [6.2, 6.4], concretization
    • Was getting 6.4
    • spack spec -U got 6.2
    • Using system nano with spack ncurses causes problem
  • Sreeram: spack info petsc doesn't show amgx
    • Looks like it wasn't added yet
    • Installing amgx has an issue
    • Resolved by pulling newer version (2.4)
  • Brian (VE): is there ever a reason for python to have a runtime dependency on py-setuptools
    • Peter: sometimes, but not all cases of declared dependencies assign the correct deptypes
    • Generating modules
    • Within a DAG, spack builds multiple py-setuptools
  • Brian (K):
  • Kevin Fotso:
    • libbsd/expat issue
    • The libbsd.so file generated by Spack is ASCII (at least as provided by file)
    • In the meantime, possibly use an external libbsd
    • Kevin: also tried symlinking libbsd.so to the actual lib
Clone this wiki locally