Graphs, digraphs, and multidigraphs in GAP

Version 1.6.1
Released 2022-12-06

This project is maintained by James Mitchell, Wilf A. Wilson

DOI Binder Build status Code coverage


Digraphs package for GAP

Getting Digraphs

To get the latest version of the package, download the archive file digraphs-x.x.x.tar.gz from the Digraphs webpage. Then, inside the pkg subdirectory of your GAP installation, unpack the archive digraphs-x.x.x.tar.gz, using

gunzip digraphs-x.x.x.tar.gz; tar xvf digraphs-x.x.x.tar

for example. This will create a subdirectory digraphs-x.x.x.


For questions, remarks, suggestions, and issues please use the issue tracker.


It is assumed that you have a working copy of GAP with version number 4.10.0 or higher. The most up-to-date version of GAP, and instructions on how to install it, can be obtained from the main GAP webpage.

The following is a summary of the steps that should lead to a successful installation of Digraphs:

Compiling the kernel module

The Digraphs package has a GAP kernel component written in C, which has to be compiled in order for the package to work. This component contains certain low-level functions that the package requires.

It is not possible to use the Digraphs package without compiling it.

To compile the kernel component inside the digraphs-x.x.x directory, type


If you installed the package in a pkg directory other than the standard pkg directory in your GAP installation, then you have to do two things. Firstly, during compilation you have to use the option --with-gaproot=PATH of the configure script where PATH is a path to the main GAP root directory (if not given, the default ../.. is assumed).

If you installed GAP on several architectures, then you must execute the configure/make step for each of the architectures. You can either do this immediately after configuring and compiling GAP itself on this architecture, or alternatively set the environment variable CONFIGNAME to the name of the configuration you used when compiling GAP before running ./configure. Note however that your compiler choice and flags (environment variables CC and CFLAGS) need to be chosen to match the setup of the original GAP compilation. For example, you have to specify 32-bit or 64-bit mode correctly!

Configuration options

In addition to the usual autoconf generated configuration flags, the following flags are provided.

Option Meaning
–enable-code-coverage enable code coverage support
–enable-compile-warnings enable compiler warnings
–enable-debug enable debug mode
–with-external-bliss use external bliss
–with-external-planarity use external planarity
–with-gaproot specify root of GAP installation
–without-intrinsics do not use compiler intrinsics even if available

Digraphs vendors the bliss and planarity libraries in the extern directory. If you wish to use your system copy of bliss or planarity, please use the configure options --with-external-bliss or --with-external-planarity, as appropriate.

If you wish to install a development version of the Digraphs package, then you must first run the command ./autogen.sh before compilation. However, development versions of the package may be unstable, and we recommend using the most recently released version of the package when possible.