From 5dc86c7fb9d05622d51ff4fba95e958983a24286 Mon Sep 17 00:00:00 2001 From: Mihai Maruseac Date: Sat, 23 Jun 2018 21:55:47 -0700 Subject: [PATCH] Document that `stack ghci` works best only after `stack build`. This documents the #2790 and #4148 bugs as we decided in #4177 to only document this behavior for 1.8.1 release and solve them later. --- doc/ghci.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/ghci.md b/doc/ghci.md index ea423f4ce6..a66bcdcf34 100644 --- a/doc/ghci.md +++ b/doc/ghci.md @@ -75,3 +75,10 @@ For doing experiments which just involve packages installed in your databases, it may be useful to run ghci plainly like `stack exec ghci`. This will run a plain `ghci` in an environment which includes `GHC_PACKAGE_PATH`, and so will have access to your databases. + +*Note*: Running `stack ghci` on a pristine copy of the code doesn't currently +build libraries +([#2790](https://github.com/commercialhaskell/stack/issues/2790)) or internal +libraries ([#4148](https://github.com/commercialhaskell/stack/issues/4148)). +It is recommended to always run a `stack build` before running `stack ghci`, +until these two issues are closed.