summaryrefslogtreecommitdiff
path: root/hadrian/doc
diff options
context:
space:
mode:
authorAndrey Mokhov <andrey.mokhov@gmail.com>2021-12-11 23:48:24 +0000
committerMarge Bot <ben+marge-bot@smart-cactus.org>2021-12-12 09:11:20 -0500
commit93783e6a8765e1410d0a14fd5249a995c6759308 (patch)
treee6d85781f873b0df6866491e3da5e64502d8ac5e /hadrian/doc
parentf04d1a4935beda0144a7b830589ab214d785d592 (diff)
downloadhaskell-93783e6a8765e1410d0a14fd5249a995c6759308.tar.gz
Drop --configure from Hadrian docs
Diffstat (limited to 'hadrian/doc')
-rw-r--r--hadrian/doc/make.md4
-rw-r--r--hadrian/doc/windows.md3
2 files changed, 2 insertions, 5 deletions
diff --git a/hadrian/doc/make.md b/hadrian/doc/make.md
index 6d20d42503..82e5ab7929 100644
--- a/hadrian/doc/make.md
+++ b/hadrian/doc/make.md
@@ -11,11 +11,9 @@ are looking for a more verbose and comprehensive document, you should head to
For GHC hackers already used to the Make build system, here is what you need to
know:
-- You can still boot and configure yourself.
+- You still need to `boot` and `configure` yourself.
- Use `hadrian/build.{sh, bat}` instead of `make`. It supports `-j`. This build
script will from now on be referred to as simply `build`.
-- Add the `-c` flag if you want hadrian to boot and configure the source tree
- for you.
- Build products are not in `inplace` anymore, but `_build` by default. Your
stage 2 GHC would then be at `_build/stage1/bin/ghc` (because it's built by
the stage 1 compiler).
diff --git a/hadrian/doc/windows.md b/hadrian/doc/windows.md
index d8fc414f3a..213bcc86c8 100644
--- a/hadrian/doc/windows.md
+++ b/hadrian/doc/windows.md
@@ -20,8 +20,7 @@ stack exec -- pacman -S autoconf automake-wrapper make patch python tar --noconf
stack build
# Build GHC
-# Note that the --configure flag is required only for the first build
-stack exec hadrian -- --directory ".." -j --flavour=quickest --configure
+stack exec hadrian -- --directory ".." -j --flavour=quickest
# Test GHC
cd ..