The Linbox Library

Purpose

The Linbox library provides functionalities for exact linear algebra. See doc/mainpage.doxy for more info.

Auto-installer for quick install

Download linbox-auto-install.sh, make it executable, and run it!

To get a list of options:

./linbox-auto-install.sh --help

Requirements:

• GNU software building tools (e.g. Debian packages autotools-dev and dh-autoreconf),
• possibly the gfortran compiler, if Fortran-based BLAS (such as OpenBLAS) are built via this script.

Examples: For instance, on a machine with an installation of GMP and OpenBLAS in the standard search paths:

./linbox-auto-install.sh --stable=yes --make-flags="-j 3" --with-blas-libs="-lopenblas"

This script will install stable versions of Givaro, fflas-ffpack, and then LinBox, in the default path (/tmp/).

To change this default folder, use the --prefix option:

./linbox-auto-install.sh --prefix="/path/to"

This will install the development versions of Givaro, fflas-ffpack, and then LinBox, in the folder /path/to/.

Here is another example fetching and installing the latest versions of GMP, Givaro, OpenBLAS, fflas-ffpack and then LinBox.

./linbox-auto-install.sh --enable-openblas=yes --enable-gmp=yes

Installation

In brief:

./configure <options>
make
make install

See INSTALL and ./configure --help for more installation information.

Availability: from github.com/linbox-team.

Requirement: FFLAS-FFPACK

Required by FFLAS-FFPACK:

• any BLAS (Fortran or C): e.g. ATLAS, OpenBLAS, BLIS, ...
• Givaro
• GMP

Optional Dependencies

• NTL,
• IML,
• FLINT,

See doc/install*html for details.

This library requires the GNU C++ compiler (gcc-4.3 or newer) or any compiler supporting advanced template features.

Authors

The LinBox group (see AUTHORS file for a list of contributors).

Citing LinBox

If your research depends on the LinBox library, please consider citing the project as

@manual{linbox,
title = {{LinBox}},
author = {The {LinBox} group},
edition = {v1.6.3},
year = {2019},
url = {http://github.com/linbox-team/linbox}
}

Contact and discussions

Corrections, suggestions and comments to [email protected]