[commit: ghc] wip/nfs-locking: Use `-B` flag to reset the build (bdb88c6)

git at git.haskell.org git at git.haskell.org
Thu Oct 26 23:29:31 UTC 2017


Repository : ssh://git@git.haskell.org/ghc

On branch  : wip/nfs-locking
Link       : http://ghc.haskell.org/trac/ghc/changeset/bdb88c61e4e0761a2ad80904f26d2443fecf7fd4/ghc

>---------------------------------------------------------------

commit bdb88c61e4e0761a2ad80904f26d2443fecf7fd4
Author: Andrey Mokhov <andrey.mokhov at gmail.com>
Date:   Fri Dec 25 22:49:45 2015 +0000

    Use `-B` flag to reset the build


>---------------------------------------------------------------

bdb88c61e4e0761a2ad80904f26d2443fecf7fd4
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c415ee4..6d27b25 100644
--- a/README.md
+++ b/README.md
@@ -51,7 +51,7 @@ Also see the [Building GHC on Windows guide][ghc-windows-building-guide].
 
 ### Resetting the build
 
-To reset the new build system delete the `shake-build/.db` directory which stores the Shake database. This will force Shake to rerun all rules, even if the 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 will force Shake to rerun all rules, even if the 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)).
 
 
 How to contribute



More information about the ghc-commits mailing list