Skip to content

[package list]

libFLAME

License information

LibFLAME is licensed under the 3-clause BSD license, a copy of which can be found in the LICENSE file in the source repository.

From version 4.0 on, a copy of the license can be found in $EBROOTLIBFLAME/share/licenses/libFLAME after installation and loading of the libFLAME module.

User-installable modules (and EasyConfigs)

Install with the EasyBuild-user module: 

eb <easyconfig> -r
To access module help after installation and get reminded for which stacks and partitions the module is installed, use module spider libFLAME/<version>.

EasyConfig:

Technical documentation

Notes

  • The regular versions use 32-bit integers in the Lapack interfaces but we also created versions with a 64-bit interface.

EasyBuild

Version 3.1 for CPE 21.08 (archived)

  • Build from the AMD branch of libFLAME but starting from the EasyBuilders EasyConfig.

Version 3.2 for CPE 22.06 and 22.08 (archived)

  • Almost straightforwared port of the 3.1 one but with a different edit of the configure script that might be more robust across versions.

  • Added --enable-amd-flags which is said to give better performance on AMD CPUs. Note that --enable-amd-aocc-flags is needed instead with the AOCC compiler. And then also added --enable-amd-opt which should take an AMD-specific code path.

  • Fixed the setup for the Cray compilers.

  • Added a cpeAOCC variant in 22.08.

Version 4.0 for CPE 22.12 (archived) and 23.03

  • EasyConfig started as a port but needed some work:

    • -march in configure is now -mtune so needed to adapt that line

    • Need to patch a python script that has the Python-interpreter hard-coded as python instead of python3. We do so with another sed in preconfigopts as the edit is so simple a ptach isn't really needed.'

Version 4.2 for CPE 23.12 and 24.03

  • Trivial port of the EasyConfig file for 4.2

Archived EasyConfigs

The EasyConfigs below are additonal easyconfigs that are not directly available on the system for installation. Users are advised to use the newer ones and these archived ones are unsupported. They are still provided as a source of information should you need this, e.g., to understand the configuration that was used for earlier work on the system.