[commit: ghc] wip/nfs-locking: Add dependencies, fix #155. (85799a5)
git at git.haskell.org
git at git.haskell.org
Fri Oct 27 00:38:14 UTC 2017
Repository : ssh://git@git.haskell.org/ghc
On branch : wip/nfs-locking
Link : http://ghc.haskell.org/trac/ghc/changeset/85799a569efbace0d6fdc168c6ddff0a015d1df8/ghc
>---------------------------------------------------------------
commit 85799a569efbace0d6fdc168c6ddff0a015d1df8
Author: Andrey Mokhov <andrey.mokhov at gmail.com>
Date: Tue Jan 12 17:25:00 2016 +0000
Add dependencies, fix #155.
[skip ci]
>---------------------------------------------------------------
85799a569efbace0d6fdc168c6ddff0a015d1df8
README.md | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index fe6a909..823e472 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ on the [wiki page][ghc-shake-wiki] and in this [blog post][shake-blog-post].
This is supposed to go into the `shake-build` directory of the GHC source tree.
-[Join us on #shaking-up-ghc on Freenode](irc://chat.freenode.net/#shaking-up-ghc)
+[Join us on #shaking-up-ghc on Freenode](irc://chat.freenode.net/#shaking-up-ghc).
Trying it
---------
@@ -23,6 +23,9 @@ identical to those for the `make` build system. This means that you don't need
to adjust anything if you are already familiar with building ghc using the `make`
build system.
+Furthermore, we depend on the following packages which need to be installed:
+`ansi-terminal`, `mtl`, `shake`, `quickcheck`.
+
### Getting the source and configuring GHC
```bash
@@ -51,7 +54,7 @@ Also see the [Building GHC on Windows guide][ghc-windows-building-guide].
### Resetting the build
-To reset the new build system run the build script with `-B` flag. This forces Shake to rerun all rules, even if results of the previous build are still in the GHC tree. This is a temporary solution; we are working on a proper reset functionality (see [#32](https://github.com/snowleopard/shaking-up-ghc/issues/32)).
+To reset the new build system run the build script with `-B` flag. This forces Shake to rerun all rules, even if results of the previous build are still in the GHC tree. This is a temporary solution; we are working on a proper reset functionality (#131).
How to contribute
More information about the ghc-commits
mailing list