... | ... | @@ -31,6 +31,31 @@ $ make stage2 |
|
|
|
|
|
For more, see [Developing in a GHC build tree](building/using#developing-in-a-ghc-build-tree).
|
|
|
|
|
|
## Cleaning
|
|
|
|
|
|
|
|
|
To clean the whole tree:
|
|
|
|
|
|
```wiki
|
|
|
$ make clean
|
|
|
```
|
|
|
|
|
|
|
|
|
there's also `make distclean`, which will clean files that are generated by `configure`, and `make maintainer-clean`, which cleans everything that is not in the source repository.
|
|
|
|
|
|
|
|
|
You can clean just a part of the tree, e.g. the RTS:
|
|
|
|
|
|
```wiki
|
|
|
$ cd rts
|
|
|
$ make clean
|
|
|
```
|
|
|
|
|
|
## Validating
|
|
|
|
|
|
|
|
|
Another way to build GHC is to [run the validate script](testing-patches), which does a build of GHC from scratch (it does `make distclean` first), using standard settings, and then runs the testsuite. If validate passes without any errors, then it is ok to submit the patches from your tree.
|
|
|
|
|
|
## Parallel builds
|
|
|
|
|
|
|
... | ... | |