Differences

This shows you the differences between two versions of the page.

--- doku:spack-transition [2023/05/05 10:35] – jz
+++ doku:spack-transition [2023/05/08 07:45] – katrin
@@ Line 1: / Line 1: @@
 ====== SPACK - migration to setup without environment  ======
-===== Problems of SPACK environments =====
+===== Motivation: problems of SPACK environments =====
 Having worked with //spack environments// for some time, we have encountered several severe issues which have convinced us that we need to find a more practical way of maintaining software packages on VSC.
@@ Line 169: / Line 169: @@
 }
 </code>
+Usage example:
+<code>
+skylake [user@l41 ~]$ spack search asd
+==> The package hash asd refers to python and belongs to vsc4 as:
+     python +bz2+ctypes+dbm~debug+libxml2+lzma~nis~optimizations+pic+pyexpat+pythoncmd+readline+shared+sqlite3+ssl~tix~tkinter~ucs4+uuid+zlib
+==> Searching similar python modules at skylake...
+---/gpfs/opt/sw/skylake/spack-0.19.0/share/spack/modules/linux-almalinux8-skylake_avx512---
+python/3.10.8-gcc-9.5.0-qh22vnd
+python/3.10.8-gcc-12.2.0-apbi5uz
+python/3.10.8-intel-2021.7.1-p4x6jid
+==> Load any one of these packages with 'module load mypackage', e.g.:
+module load python/3.10.8-intel-2021.7.1-p4x6jid
+==> Get some additional info with 'spack find -lvd mypackage', e.g.:
+spack find -lvd /p4x6ji
+</code>
+----
@@ Line 186: / Line 210: @@
 <box 80% round red|Warning>This approach is not recommended and we will no longer maintain the spack environments or install new packages there</box>
+===== Continue working with old spack environments =====
+You may also continue to work with the spack environments. If you wish to do so you need the following commands:
+==== On zen3 ====
+<code>
+source /opt/sw/spack-0.17.1/share/spack/setup-env.sh
+spacktivate zen3
+</code>
+==== On skylake ====
+<code>
+source /opt/sw/spack-0.19.0/share/spack/setup-env.sh
+spacktivate skylake
+</code>
+<box 80% round red|Warning>This approach is not recommended and we will no longer maintain the spack environments or install new packages there</box>
 ----
@@ Line 209: / Line 255: @@
 ----
-===== Setting LD_LIBRARY_PATH =====
+==== Setting LD_LIBRARY_PATH ====
 Loading a module does no longer automatically set the ''LD_LIBRARY_PATH'' environment variable, as with some software packages this has lead to conflicts with system libraries. If you have to set ''LD_LIBRARY_PATH'' you may use: