You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Julian Ospald 3e841b3c68
Merge branch 'settings' into master
2 years ago
.gitlab Add stack.yaml wrt #75 3 years ago
.travis Fix stripping in travis 3 years ago
3rdparty Remove unnecessary bundles 3 years ago
app Allow configuring URLSource as well 2 years ago
golden Update golden test 2 years ago
lib Allow configuring URLSource as well 2 years ago
shell-completions Add zsh and fish completion wrt #19 3 years ago
test Add JSON roundtrip specs 3 years ago
www Improve style 3 years ago
.gitignore Update .gitignore 3 years ago
.gitlab-ci.yml Upload golden files as artifacts on failure 2 years ago
.travis.yml Try to build for El Capitan 3 years ago Allow to configure ghcup with a yaml config file 2 years ago First cross try 3 years ago
LICENSE Initial commit 3 years ago Allow configuring URLSource as well 2 years ago Use yaml instead of pesky json 3 years ago
Setup.hs Initial commit 3 years ago Cleanup 3 years ago
bootstrap-haskell Bump ghcup version in bootstrap-haskell 2 years ago
cabal.ghc884.project Update to versions-4.0.1 API 2 years ago
cabal.ghc884.project.freeze Update to versions-4.0.1 API 2 years ago
cabal.project Remove text-conversion workaround 2 years ago
config.yaml Allow configuring URLSource as well 2 years ago
ghcup-0.0.2.yaml update to cabal- 2 years ago
ghcup-0.0.3.yaml update to cabal- 2 years ago
ghcup.cabal Allow to configure ghcup with a yaml config file 2 years ago
hie.yaml Update hie.yaml 2 years ago
stack.yaml Update to versions-4.0.1 API 2 years ago

ghcup makes it easy to install specific versions of ghc on GNU/Linux, macOS (aka Darwin) and FreeBSD and can also bootstrap a fresh Haskell developer environment from scratch. It follows the unix UNIX philosophy of do one thing and do it well.

Similar in scope to rustup, pyenv and jenv.

Ubuntu users may prefer hvr’s ppa.

Table of Contents


Simple bootstrap

Follow the instructions at

Manual install

Download the binary for your platform at and place it into your PATH anywhere.

Then adjust your PATH in ~/.bashrc (or similar, depending on your shell) like so:

export PATH="$HOME/.cabal/bin:$HOME/.ghcup/bin:$PATH"

Vim integration

See ghcup.vim.


See ghcup --help.

For the simple interactive TUI, run:

ghcup tui

For the full functionality via cli:

# list available ghc/cabal versions
ghcup list

# install the recommended GHC version
ghcup install ghc

# install a specific GHC version
ghcup install ghc 8.2.2

# set the currently "active" GHC version
ghcup set ghc 8.4.4

# install cabal-install
ghcup install cabal

# update ghcup itself
ghcup upgrade

Generally this is meant to be used with cabal-install, which handles your haskell packages and can demand that a specific version of ghc is available, which ghcup can do.


A configuration file can be put in ~/.ghcup/config.yaml. The default config file explaining all possible configurations can be found in this repo: config.yaml.

Partial configuration is fine. Command line options always overwrite the config file settings.


For man pages to work you need man-db as your man provider, then issue man ghc. Manpages only work for the currently set ghc. MANPATH may be required to be unset.


Shell completions are in shell-completions.

For bash: install shell-completions/bash as e.g. /etc/bash_completion.d/ghcup (depending on distro) and make sure your bashrc sources the startup script (/usr/share/bash-completion/bash_completion on some distros).

Cross support

ghcup can compile and install a cross GHC for any target. However, this requires that the build host has a complete cross toolchain and various libraries installed for the target platform.

Consult the GHC documentation on the prerequisites. For distributions with non-standard locations of cross toolchain and libraries, this may need some tweaking of or configure args. See ghcup compile ghc --help for further information.

XDG support

To enable XDG style directories, set the environment variable GHCUP_USE_XDG_DIRS to anything.

Then you can control the locations via XDG environment variables as such:

  • XDG_DATA_HOME: GHCs will be unpacked in ghcup/ghc subdir
  • XDG_CACHE_HOME: logs and download files will be stored in ghcup subdir
  • XDG_BIN_HOME: binaries end up here (default: ~/.local/bin)

Installing custom bindists

There are a couple of good use cases to install custom bindists:

  1. manually built bindists (e.g. with patches)
  • example: ghcup install ghc -u 'file:///home/mearwald/tmp/ghc-eff-patches/ghc-8.10.2-x86_64-deb10-linux.tar.xz' 8.10.2-eff
  1. GHC head CI bindists
  • example: ghcup install ghc -u '' head
  1. DWARF bindists
  • example: ghcup install ghc -u '' 8.10.2-dwarf

Since the version parser is pretty lax, 8.10.2-eff and head are both valid versions and produce the binaries ghc-8.10.2-eff and ghc-head respectively. GHCup always needs to know which version the bindist corresponds to (this is not automatically detected).

Design goals

  1. simplicity
  2. non-interactive
  3. portable (eh)
  4. do one thing and do it well (UNIX philosophy)


  1. invoking sudo, apt-get or any package manager
  2. handling system packages
  3. handling cabal projects
  4. being a stack alternative


Installs a specified GHC version into ~/.ghcup/ghc/<ver>, and places ghc-<ver> symlinks in ~/.ghcup/bin/.

Optionally, an unversioned ghc link can point to a default version of your choice.

This uses precompiled GHC binaries that have been compiled on fedora/debian by upstream GHC.

Alternatively, you can also tell it to compile from source (note that this might fail due to missing requirements).

In addition this script can also install cabal-install.

Known users

Known problems

Custom ghc version names

When installing ghc bindists with custom version names as outlined in installing custom bindists, then cabal might be unable to find the correct ghc-pkg (also see #73) if you use cabal build --with-compiler=ghc-foo. Instead, point it to the full path, such as: cabal build --with-compiler=$HOME/.ghcup/ghc/<version-name>/bin/ghc or set that GHC version as the current one via: ghcup set ghc <version-name>.

This problem doesn’t exist for regularly installed GHC versions.

Limited distributions supported

Currently only GNU/Linux distributions compatible with the upstream GHC binaries are supported.

Precompiled binaries

Since this uses precompiled binaries you may run into several problems.

Missing libtinfo (ncurses)

You may run into problems with ncurses and missing libtinfo, in case your distribution doesn’t use the legacy way of building ncurses and has no compatibility symlinks in place.

Ask your distributor on how to solve this or try to compile from source via ghcup compile <version>.

Libnuma required

This was a bug in the build system of some GHC versions that lead to unconditionally enabled libnuma support. To mitigate this you might have to install the libnuma package of your distribution. See here for a discussion.


Although this script can compile GHC for you, it’s just a very thin wrapper around the build system. It makes no effort in trying to figure out whether you have the correct toolchain and the correct dependencies. Refer to the official docs on how to prepare your environment for building GHC.


  1. Why reimplement stack?

ghcup is not a reimplementation of stack. The only common part is automatic installation of GHC, but even that differs in scope and design.

  1. Why not support windows?

Consider using Chocolatey or ghcups.

  1. Why the haskell reimplementation?

Why not?