|Julian Ospald 46da6f3d6d||1 year ago|
|.gitlab||1 year ago|
|.requirements/ghc||1 year ago|
|www||1 year ago|
|.available-versions||1 year ago|
|.bash-completion||2 years ago|
|.download-urls||1 year ago|
|.gitlab-ci.yml||1 year ago|
|CHANGELOG.md||1 year ago|
|CONTRIBUTING.md||2 years ago|
|COPYING||3 years ago|
|README.md||1 year ago|
|bootstrap-haskell||1 year ago|
|generate_changelog.sh||1 year ago|
|ghcup||1 year ago|
ghcup makes it easy to install specific versions of
ghc on GNU/Linux as well as macOS (aka Darwin), 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.
Ubuntu users may prefer hvr’s ppa.
Choose one of the following installation methods.
# complete bootstrap curl https://gitlab.haskell.org/haskell/ghcup/raw/master/bootstrap-haskell -sSf | sh # prepare your environment . "$HOME/.ghcup/env" echo '. $HOME/.ghcup/env' >> "$HOME/.bashrc" # or similar # now create a project, such as: mkdir myproject && cd myproject cabal init -n --is-executable cabal v2-run
Just place the
ghcup shell script into your
( mkdir -p ~/.ghcup/bin && curl https://gitlab.haskell.org/haskell/ghcup/raw/master/ghcup > ~/.ghcup/bin/ghcup && chmod +x ~/.ghcup/bin/ghcup) && echo "Success"
Then adjust your
~/.bashrc (or similar, depending on your shell) like so, for example:
Security aware users may want to use the files from the release page and verify the gpg signatures.
Common use cases are:
# install the last known "best" GHC version ghcup install # install a specific GHC version ghcup install 8.2.2 # set the currently "active" GHC version ghcup set 8.4.4 # install cabal-install ghcup install-cabal # update cabal-install cabal new-install cabal-install
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.
apt-getor any package manager
Installs a specified GHC version into
~/.ghcup/ghc/<ver>, and places
ghc-<ver> symlinks in
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
Currently only GNU/Linux distributions compatible with the upstream GHC binaries are supported.
Since this uses precompiled binaries you may run into several problems.
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>.
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.
ghcup is not a reimplementation of stack. The only common part is automatic installation of GHC, but even that differs in scope and design.
While this might be an interesting idea, ghcup is about simplicity.
ghcup is POSIX sh.
Mainly because the implementation is fairly straight-forward and the script is highly portable. No need to bootstrap anything or set up yet another CI to build ghcup binaries for all possible arches and distros just to perform a very simple task: identify distro and platform and download a GHC bindist.