Meta tags:
description=A program for developing Haskell projects. ;
author=Stack contributors;

Headings (most frequently used words):

the, stack, setup, command,

Text of the page (most frequently used words):
the (45), stack (33), ghc (30), and (23), libc6 (14), version (13), install (12), with (10), that (10), binary (10), distribution (10), are (10), present (10), not (8), setup (8), for (7), windows (7), versions (7), build (7), linux (7), project (7), configuration (7), will (6), directory (6), files (6), file (6), compatible (6), tinfo6 (6), libgmp (6), different (6), indicate (5), musl (5), library (5), option (5), permission (4), system (4), default (4), those (4), distributions (4), libtinfo (4), libc (4), provided (4), libraries (4), available (4), flag (4), variant (4), attempt (4), package (4), commands (4), contributors (3), user (3), account (3), have (3), create (3), temporary (3), root (3), drive (3), long (3), paths (3), location (3), require (3), pre232 (3), this (3), gnu (3), example (3), particular (3), msys2 (3), url (3), non (3), specific (3), options (3), more (3), get (3), involved (3), integration (3), building (3), topics (3), configure (3), getting (3), started (3), made (2), but (2), standard (2), may (2), uses (2), zip (2), from (2), downloaded (2), does (2), applicable (2), consequently (2), enabled (2), used (2), fedora (2), later (2), libncursesw (2), use (2), x86_64 (2), these (2), shared (2), terminal (2), handling (2), required (2), certain (2), one (2), passing (2), command (2), msys (2), false (2), pass (2), specify (2), installed (2), bindist (2), already (2), reinstall (2), ghcjs (2), boot (2), clean (2), glossary (2), faq (2), how (2), works (2), upgrading (2), maintainers (2), code (2), docker (2), script (2), cabal (2), snapshot (2), environment (2), flags (2), projects (2), setting (2), welcome (2), github (2), material, mkdocs, copyright, 2015, 2025, back, top, usually, type, administrator, convention, well, tool, decompress, extract, tools, archive, aiming, avoid, named, final, destination, either, where, needs, tmp, hash, since, 1607, has, been, capable, capability, assume, being, builds, debian, rocky, associates, gmp4, ncurses6, should, alpine, low, level, terminfo, wide, character, support, multiple, precision, arithmetic, glibc, designed, backwards, considers, attempting, identify, refer, presence, absence, there, many, make, another, depend, which, need, configured, then, warn, inconsistent, take, action, requires, specifying, custom, further, information, about, see, documentation, only, disabled, regardless, whether, argument, attempts, ghc_version, ghcjs_boot, history, other, resources, overview, signing, key, self, hosted, runners, haskellstack, org, add, maintainer, team, process, releases, scheme, dev, containers, contributor, guide, haskell, lock, azure, travis, shell, auto, completion, developing, visual, studio, editor, debugging, source, initialization, nix, interpreter, yaml, specification, work, directories, customisation, scripts, global, include, directive, variables, upload, upgrade, update, unpack, uninstall, test, templates, sdist, runhaskell, runghc, run, repl, query, purge, path, new, list, init, ide, hpc, hoogle, haddock, ghci, exec, eval, dot, config, bench, conclusion, using, interactively, executing, locations, multi, targets, synonyms, databases, existing, your, description, hello, world, initializing, search, skip, content,

Text of the page (random words):
setup stack skip to content stack setup initializing search github welcome setting up getting started commands configure topics get involved faq glossary more stack github welcome setting up getting started getting started 1 a hello world example 2 package description 3 project configuration 4 building your project 5 building existing projects 6 installed package databases 7 stack build synonyms 8 stack build targets 9 multi package projects 10 cabal flags and ghc options 11 locations used by stack 12 executing commands 13 using ghc interactively 14 stack configuration 15 in conclusion commands commands bench build clean config dot docker eval exec ghc ghci haddock hoogle hpc ide init install list ls new path purge query repl run runghc runhaskell script sdist setup templates test uninstall unpack update upgrade upload configure configure environment variables configuration files configuration files project specific configuration non project specific configuration the include directive global flags and options customisation scripts topics topics stack root stack work directories stack environment snapshot location package location snapshot specification stack yaml vs a cabal file script interpreter docker integration nix integration non standard project initialization building ghc from source debugging editor integration stack and visual studio code developing on windows shell auto completion ci travis ci azure ci lock files haskell and c code get involved get involved contributors contributors contributor s guide dev containers maintainers maintainers version scheme releases maintainer team process add ghc version upgrading msys2 upgrading 7 zip haskellstack org self hosted runners signing key how stack works how stack works build overview faq glossary more more other resources version history the stack setup command stack setup ghc_version no reinstall ghc bindist url ghcjs boot options ghcjs_boot no ghcjs boot clean stack setup attempts to install a version of ghc and on windows msys2 by default the version of ghc is the one required by the project specify the version of ghc as an argument to attempt to install a different version of ghc for example stack setup 9 10 3 will attempt to install ghc 9 10 3 and an attempt to install is made only if the version of ghc is not already available to stack pass the flag reinstall disabled by default to attempt to install the version of ghc regardless of whether it is already available to stack pass the option ghc bindist url to specify the url of the ghc to be downloaded and installed this option requires the use of the ghc variant option specifying a custom ghc variant for further information about the ghc variant option see the ghc variant non project specific configuration option documentation if stack is configured not to install ghc install ghc false or passing the no install ghc flag or not to install msys2 install msys false or passing the no install msys flag then stack setup will warn that the flag and the command are inconsistent and take no action linux windows a particular binary distribution of ghc will depend on certain libraries which need to be available there are many different linux distributions and different versions of a particular linux distribution one linux distribution version may make available different libraries to another linux distribution version in attempting to identify the particular binary distribution of ghc that is required on linux stack will refer to the presence or absence of certain libraries or the versions of those libraries for example stack 3 1 1 considers if libc musl x86_64 so 1 is present this file is provided by the musl libc 2 13 1 the version of libc6 if musl libc is not applicable the gnu c library glibc that is present the gnu c library is designed to be backwards compatible 2 11 1 if libgmp so 3 or libgmp so 10 is present these files are provided by different versions of the gnu multiple precision arithmetic library if libncursesw so 6 is present this file is provided by a shared library for terminal handling with wide character support if libtinfo so 5 or libtinfo so 6 is present these files are provided by different versions of a shared low level terminfo library for terminal handling stack 3 1 1 uses ghc build musl to indicate libc musl x86_64 so 1 is present and stack should use the ghc binary distribution for alpine linux tinfo6 to indicate libgmp so 10 and libtinfo so 6 are present and libc6 is compatible with libc6 2 32 tinfo6 libc6 pre232 to indicate libgmp so 10 and libtinfo so 6 are present and libc6 is not compatible with libc6 2 32 ncurses6 to indicate libgmp so 10 and libncursesw so 6 are present gmp4 to indicate libgmp so 3 is present by default stack associates the tinfo6 build with the fedora 33 binary distribution of ghc 9 4 1 to 9 4 3 and 9 6 1 and later those binary distributions require versions of libc6 that are compatible with libc6 2 32 the tinfo6 libc6 pre232 build with the debian 10 binary distribution of ghc 9 4 1 to 9 4 3 and the rocky 8 binary distribution of ghc 9 6 1 and later those binary distributions require versions of libc6 that are compatible with libc6 2 28 and the tinfo6 and tinfo6 libc6 pre232 builds with the fedora 27 binary distribution of ghc 9 4 4 to 9 4 8 those binary distributions require versions of libc6 that are compatible with libc6 2 26 since windows 10 version 1607 windows has been long file paths capable but that capability is not enabled by default consequently stack does not assume that it is being used on a system that is long file paths enabled stack uses the 7 zip tool to decompress and extract tools from downloaded archive files aiming to avoid long file paths stack does so in a temporary directory named stack tmp hash on the drive of the final destination either in the system temporary directory where applicable or the root of the drive consequently stack needs permission to create a directory in that location a windows user account will usually have permission to create a directory in the system temporary directory a windows user account of type administrator will have permission to create a directory in the root of the system drive c by convention but a standard user account may well not have permission back to top copyright c 2015 2025 stack contributors made with material for mkdocs