| Both sides previous revision Previous revision Next revision | Previous revision |
| habrok:migration:alma9:start [2026/07/06 08:30] – pedro | habrok:migration:alma9:start [2026/09/07 07:14] (current) – [Self-compiled applications] admin |
|---|
| ====== Hábrók upgrade from Alma Linux 8 to 9 ====== | ====== Hábrók upgrade from Alma Linux 8 to 9 ====== |
| |
| <WRAP todo round> **The AlmaLinux 9 test environment is currently disabled** | |
| |
| Due to an identified security vulnerability, the AlmaLinux 9 nodes have been temporarily disabled. \\ | |
| This includes the login node ''merel1'', and compute nodes ''vink[1,2]'' and ''groenling1''. | |
| You can follow our [[https://status.hpc.rug.nl/issue/cfa95f11-bf88-43bf-8595-88648e8a0d3b|status page]] for updates on this issue. | |
| </WRAP> | |
| |
| 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: | 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: |
| ==== Self-compiled applications ==== | ==== 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 ==== | ==== Personal Python and R libraries ==== |
| |