Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Mirror of ghc repository. DO NOT SUBMIT PULL REQUESTS HERE. Patches are best submitted to GHC's Phabricator (https://phabricator.haskell.org/), bugs and feature-requests are best filed to GHC's Trac (https://ghc.haskell.org/trac/ghc), or sent to the mailing list (ghc-devs@haskell.org)
Haskell C Makefile Perl6 Perl Logos Other
Branch: master

Injective type families

For details see #6018, Phab:D202 and the wiki page:

https://ghc.haskell.org/trac/ghc/wiki/InjectiveTypeFamilies

This patch also wires-in Maybe data type and updates haddock submodule.

Test Plan: ./validate

Reviewers: simonpj, goldfire, austin, bgamari

Subscribers: mpickering, bgamari, alanz, thomie, goldfire, simonmar,
             carter

Differential Revision: https://phabricator.haskell.org/D202

GHC Trac Issues: #6018
latest commit 374457809d
@jstolarek jstolarek authored
Failed to load latest commit information.
bindisttest Follow-up to 32f41c7
compiler Injective type families
distrib Build system: delete unused distrib/Makefile
docs Injective type families
driver Build system: simplify install.mk.in
ghc Respect GHC_CHARENC environment variable #10762
includes Build system: simplify install.mk.in
libffi-tarballs @ b6658e5 Update libffi-tarballs submodule to libffi 3.1 (re #8701)
libffi Build system: delete half-baked Cygwin support
libraries Injective type families
mk Build system: simplify install.mk.in
nofib @ 85d10a4 update submodule
rts RTS: Reduce MBLOCK_SPACE_SIZE on AArch64
rules Build system: simplify install.mk.in
testsuite Injective type families
utils Injective type families
.arcconfig Fix .arcconfig
.arclint Cabal submodule update: hole support and tests.
.gitignore Ignore temporary ./configure files.
.gitmodules Delete old-{time,locale} and haskell{98,2010}
.mailmap Update .mailmap [skip ci]
.travis.yml Testsuite: by default run all tests for a single way
ANNOUNCE Globally replace "hackage.haskell.org" with "ghc.haskell.org"
HACKING.md Make configure error out on missing ghc-tarballs on Windows
INSTALL.md Make configure error out on missing ghc-tarballs on Windows
LICENSE Reorganisation of the source tree
MAKEHELP.md Build system: add `make show!` command (#7810)
Makefile Testsuite: by default run all tests for a single way
README.md Make configure error out on missing ghc-tarballs on Windows
Vagrantfile vagrant: move files around
aclocal.m4 Build system: delete half-baked Cygwin support
boot Remove all references to sync-all
config.guess Update config.{guess,sub} to GNU automake 1.14.1
config.sub Update config.{guess,sub} to GNU automake 1.14.1
configure.ac configure.ac: Allow disabling of large-address-space
ghc.mk Build system: simplify install.mk.in
install-sh Update aux files `config.{guess,sub}` and `install-sh`
packages Remove all references to sync-all
settings.in LlvmCodeGen cross-compiling fixes (#9895)
validate Testsuite: by default run all tests for a single way

README.md

The Glasgow Haskell Compiler

Build Status

This is the source tree for GHC, a compiler and interactive environment for the Haskell functional programming language.

For more information, visit GHC's web site.

Information for developers of GHC can be found on the GHC Trac.

Getting the Source

There are two ways to get a source tree:

  1. Download source tarballs

    Download the GHC source distribution:

      ghc-<version>-src.tar.bz2
    

    which contains GHC itself and the "boot" libraries.

  2. Check out the source code from git

    $ git clone --recursive git://git.haskell.org/ghc.git
    

    Note: cloning GHC from Github requires a special setup. See Getting a GHC repository from Github.

    DO NOT submit pull request directly to the github repo. See the GHC team's working conventions re how to contribute a patch to GHC.

Building & Installing

For full information on building GHC, see the GHC Building Guide. Here follows a summary - if you get into trouble, the Building Guide has all the answers.

Before building GHC you may need to install some other tools and libraries. See, Setting up your system for building GHC.

NB. In particular, you need GHC installed in order to build GHC, because the compiler is itself written in Haskell. You also need Happy, Alex, and Cabal. For instructions on how to port GHC to a new platform, see the GHC Building Guide.

For building library documentation, you'll need Haddock. To build the compiler documentation, you need a good DocBook XML toolchain and dblatex.

Quick start: the following gives you a default build:

$ ./boot
$ ./configure
$ make         # can also say 'make -jX' for X number of jobs
$ make install

On Windows, you need an extra repository containing some build tools. These can be downloaded for you by configure. This only needs to be done once by running:

$ ./configure --enable-tarballs-autodownload

(NB: Do you have multiple cores? Be sure to tell that to make! This can save you hours of build time depending on your system configuration, and is almost always a win regardless of how many cores you have. As a simple rule, you should have about N+1 jobs, where N is the amount of cores you have.)

The ./boot step is only necessary if this is a tree checked out from git. For source distributions downloaded from GHC's web site, this step has already been performed.

These steps give you the default build, which includes everything optimised and built in various ways (eg. profiling libs are built). It can take a long time. To customise the build, see the file HACKING.

Filing bugs and feature requests

If you've encountered what you believe is a bug in GHC, or you'd like to propose a feature request, please let us know! Submit a ticket in our bug tracker and we'll be sure to look into it. Remember: Filing a bug is the best way to make sure your issue isn't lost over time, so please feel free.

If you're an active user of GHC, you may also be interested in joining the glasgow-haskell-users mailing list, where developers and GHC users discuss various topics and hang out.

Hacking & Developing GHC

Once you've filed a bug, maybe you'd like to fix it yourself? That would be great, and we'd surely love your company! If you're looking to hack on GHC, check out the guidelines in the HACKING.md file in this directory - they'll get you up to speed quickly.

Contributors & Acknowledgements

GHC in its current form wouldn't exist without the hard work of its many contributors. Over time, it has grown to include the efforts and research of many institutions, highly talented people, and groups from around the world. We'd like to thank them all, and invite you to join!

Something went wrong with that request. Please try again.