The following packages contain the latest major-number release of
Releases have been tested on specific operating system versions. Though some packages can be installed on newer or older systems, we advise against doing this. If you find a problem, please contact us (see at bottom of page of how to do this).
The packages below have been build against the following libraries which need to be available on the system in order to install the compiler:
We also have some user-contributed packages — as these are packages outwith the project, we can not provide any support on these. Please communicate with the package maintainers.
These packages are of the most recent (bleeding-edge) state of the compiler. They are provided on a best-effort basis, but it is highly likely that the packages (and compiler) might not work correctly and negatively impact your system. You have been warned!
rpm release of the compiler is designed to be installed on RedHat based distributions of Linux (e.g. RedHat, CentOS, Fedora, etc.) using the
rpm tool set.
$ sudo rpm --install sac2c-VERSION-RELEASE.rpm
deb package is meant to be installed on Debian based distributions (e.g. Debian, Ubuntu, etc.) using the
dpkg tool set.
$ sudo dpkg --install sac-VERSION-RELEASE.deb
pkg is a installer that will place the SaC files in the correct location on your system. Symbolic links to the SaC binaries are created in
/usr/local/bin for your convenience.
The SaC binaries are postfixed by their release type (production or debug), so there is a
sac2c is simply a link to
sac2c_pshould be in your
.tar.gz archive is the most basic distributable package that available. The archive contains the entire directory structure of the binaries and libraries as they should appear on the file-system of the host from the root directory (i.e.
/). The default directory structure is prefixed with
Installation of the compiler is as simple as extracting from the archive:
$ sudo tar --strip-components=1 -C / -xzf sac2c-VERSION-RELEASE.tar.gz
Interested in contributing to the project? You can do so in several ways, by either telling us about bugs or by contributing code to the project.
Head over to the community page and follow the guidelines there on how to submit a bug.
The standard library comes as a collection of public repositories on github/SacBase.
In the case of the source code, you'll have to check out the latest versions of the the
stdlib repository and possibly further repositories from
SacBase, you need to build and install the standard library.
Normally, the install of the stdlib should work fine in which case may want to proceed to the
If you are curious about the details on where the built modules are actually stored or on how platform dependent versions are created and kept apart you can read up about cross compilation and the SBI (SaC Binary Interface).