-
Notifications
You must be signed in to change notification settings - Fork 100
Installation Troubleshooting
The trickiest part of the installation is building the shared binaries like codex and goc-mod. Although the installer builds them each in their own Cabal sandbox it can run into problems if there are too many packages installed globally. Global packages are shared with sandboxes and affect the Cabal planner.
To see what packages you have installed, run ghc-pkg list. You shouldn't have more than these base packages installed globally:
Cabal, array, base, bin-package-db, binary, bytestring, containers, deepseq, directory, filepath, ghc, ghc-prim, haskell2010, haskell98, hoopl, hpc, integer-gmp, old-locale, old-time, pretty, process, rts, template-haskell, time, transformers, unix
If you have others, get rid of them with ghc-pkg unregister.
If the installation stops while building ghc-mod and uses the CPU but makes no progress then you're probably running it with too little memory. If you're using a virtual machine try bumping the memory to at least two gigabytes for the duration of the installation. If you cannot control the available memory, try creating a swap file as discussed here.