Skip to content

[chore] adjust readme to save users some hours #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MangoIV wants to merge 1 commit into from
Closed

[chore] adjust readme to save users some hours #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,9 @@ An impact assessment is due when

The procedure is as follows:

1. Rebase changes, mandated by your proposal, atop of `ghc-9.10` branch.
1. Rebase changes, mandated by your proposal, atop of `ghc-9.10.2` tag. Mind: the branch `ghc-9.10` is not okay since different minor versions
Comment thread
tbidne marked this conversation as resolved.
may ship different boot libraries. Mind that you want to probably also use the default flavour (not e.g. `devel2` as that may also cause
issues)

2. Compile a patched GHC, say, `~/ghc/_build/stage1/bin/ghc`.

Expand All @@ -36,6 +38,8 @@ The procedure is as follows:
* You can interrupt `cabal` at any time and rerun again later.
* Consider setting `--jobs` to retain free CPU cores for other tasks.
* Full build requires roughly 7 Gb of free disk space.
* if the build fails with an error about max amount of arguments in `gcc`, run again,
but with smaller batch size. 250 worked well for me.

To get an idea of the current progress, we can run the following commands
on the log file:
Expand Down