Differences

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

--- habrok:migration:alma9:start [2026/06/10 11:55] – [TLDR] pedro
+++ habrok:migration:alma9:start [2026/09/07 07:14] (current) – [Self-compiled applications] admin
@@ Line 1: / Line 1: @@
 ====== Hábrók upgrade from Alma Linux 8 to 9 ======
 This page covers a general overview of Hábrók's move to Alma Linux 9 and what it means for your software. Make sure you also check the following related pages:
@@ Line 8: / Line 9: @@
 ----
-===== TLDR =====
+===== TL;DR =====
 Hábrók's OS is currently Alma Linux 8.10 and we will start a migration to Alma Linux 9.8 on a date to be announced soon. This migration will be gradual and we will first set up a test environment for our users. After the initial test period we will gradually migrate login, interactive and compute nodes from Alma Linux 8 to 9. This means there will be a mixed environment for a while, see [[habrok:migration:alma9:plan|here]] for details, including on how to access a particular Alma Linux version.
@@ Line 77: / Line 78: @@
 ==== Self-compiled applications ====
-Binary applications, compiled on Alma Linux 8, may still  work on Alma Linux 9. We strongly encourage you to recompile these applications. Applications built with the OS compilers can be recompiled on Alma Linux 9 directly. Applications that have been built using compiler modules from the ''2023.01'' software stack should be recompiled using a compiler from ''EESSI/2025.06''.
+Binary applications, compiled on Alma Linux 8, may still  work on Alma Linux 9. We strongly encourage you to recompile these applications. Applications built with the OS compilers can be recompiled on Alma Linux 9 directly. Applications that have been built using compiler modules from the ''2023.01'' software stack should be recompiled using a compiler from EESSI (e.g. ''EESSI/2025.06''). Note that compiling applications with compilers from EESSI require you to load the ''buildenv'' module for the corresponding compiler toolchain, e.g. for ''foss/2025b'' you would need to load ''buildenv/default-foss-2025b''. This is a wrapper module ensuring that the compilers insert the path to dependencies into your binaries. Compiling without this module could lead to the following kind of error when running your executable:
+<code>
+error while loading shared libraries: libsomelibrary.so: cannot open shared object file: No such file or directory
+</code>
 ==== Personal Python and R libraries ====
 === Python libraries ===
-Most Python libraries are distributed as binary wheels. These binary wheels are expected to work on Alma Linux 9. Some wheels that no longer supported Alma Linux 8, may even work again on Alma Linux 9.
+Most [[..:..:software_environment:python|]] libraries are distributed as binary wheels. These binary wheels are expected to work on Alma Linux 9. Some wheels that no longer supported Alma Linux 8, may even work again on Alma Linux 9.
-We do advise you to reinstall your virtual environments with a Python version from the ''EESSI/2025.06'' software stack, as the ''2023.01''  software stack will be deprecated in the future.  See [[habrok:software_environment:eessi|here]] for more details on EESSI).
+We do advise you to reinstall your virtual environments with a Python version from the ''EESSI/2025.06'' software stack, as the ''2023.01''  software stack will be deprecated in the future.  See [[habrok:software_environment:eessi|here]] for more details on EESSI). Reinstalling your virtual environments is similar to the process of installing them in the first place. You can find detailed information on how to do this in the [[..:..:software_environment:python:environments|]] page.
 === R libraries ===