使用 Homebrew, apk, chocolatey, apt, dnf, MacPorts, Nix, pacman, zypper 安装 ghc

项目链接

• 主页
• 仓库
• 上游文档
• 软件包管理器页面

命令和别名

• ghc
• ghc-9.14.1
• ghc-pkg
• ghc-pkg-9.14.1
• ghci
• ghci-9.14.1
• haddock
• haddock-ghc-9.14.1
• hp2ps
• hp2ps-ghc-9.14.1
• hpc
• hpc-ghc-9.14.1
• hsc2hs
• hsc2hs-ghc-9.14.1
• runghc
• runghc-9.14.1
• runhaskell
• runhaskell-9.14.1

项目历史

GHC began at the University of Glasgow near the beginning of the 1990s as an academic research project funded by the UK government. Its stated goals were practical as well as academic: make a robust and portable Haskell compiler freely available, provide a modular foundation for compiler research, and learn from real programs.

The compiler evolved into a self-hosted Haskell implementation with three major pieces: the compiler, boot libraries, and the runtime system. The runtime system became central to GHC's identity because it handles garbage collection, scheduling, profiling, exceptions, and the execution machinery linked into compiled Haskell programs.

采用历史

GHC became the dominant implementation around which the Haskell ecosystem organized. The AOSA chapter by Simon Marlow and Simon Peyton Jones described hundreds of thousands of downloads, thousands of Hackage packages, undergraduate teaching use, and commercial use; the GHC site likewise points users to Hackage libraries, Haskell Language Server, Cabal, Stack, and GHCup.

The Homebrew `ghc` formula packages the general GHC track for macOS users, while separate versioned formulae let projects select older or branch-specific compiler lines. That split mirrors the way Haskell projects often pin compiler versions because language extensions, boot libraries, and package ABI compatibility can matter.

使用方式

Practitioners use `ghc` for batch compilation, `ghci` for interactive development, `runghc` or `runhaskell` for scripts, `ghc-pkg` for package database inspection, and Haddock for API documentation. The user guide presents GHC as one program that can operate as either an interactive interpreter or a batch compiler.

Build tools such as Cabal and Stack commonly invoke GHC rather than requiring users to call every compiler flag by hand. Advanced users still care about GHC flags directly for optimisation, profiling, language extensions, cross-platform builds, and debugging package database or linker issues.

为什么软件包爱好者会关心

GHC is package-manager significant because it is both a compiler and a dependency root for much of the Haskell toolchain. Installing the formula affects not only `ghc`, but also GHCi, boot libraries, package metadata, Haddock, profiling tools, and the versioned executable names that allow scripts to target a specific compiler.

The project also embodies a classic language-runtime packaging problem: the compiler is written in Haskell and needs an existing GHC to build, while libraries compiled by one branch may need rebuilding for another. Versioned formulae, GHCup metadata, and project-level pinning all grew around those realities.

时间线

• 1990: Haskell was created as a common lazy functional language for research.
• Early 1990s: GHC began as a Glasgow research project with portability, performance, and extensibility goals.
• 2007: The GHC user guide documented the even-numbered stable-branch versioning policy starting with GHC 6.8.
• 2011: The AOSA chapter described GHC as an industrial-strength compiler used in teaching, research, and commercial settings.
• 2025: GHC 9.14.1 release artifacts provided the branch represented by the unversioned Homebrew executable names in this batch input.

Related projects

• Hackage is the package repository that distributes Haskell libraries built for use with GHC and other tooling.
• GHCup is the Haskell installer that installs GHC along with related tools.
• Cabal, Stack, Haddock, Happy, Alex, and Haskell Language Server form the surrounding toolchain named by GHC's own documentation.

来源

• https://downloads.haskell.org/ghc/9.14.1/docs/users_guide/intro.html
• https://formulae.brew.sh/formula/ghc
• https://gitlab.haskell.org/ghc/ghc
• https://www.aosabook.org/en/v2/ghc.html
• https://www.haskell.org/ghc/
• https://www.haskell.org/ghcup/