Skip to content
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.

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

ghc: Use 8.2.2 binary for boot, no parallel builds on aarch64. #45166

Closed
wants to merge 1 commit into from

Conversation

TravisWhitaker
Copy link
Contributor

Motivation for this change

GHC 8.2.1 is rather broken. Upstream's build system actually complains if you attempt to build with it (see this bug). This is especially true of aarch64. It would be nice to bootstrap with upstream's binary 8.2.2 instead.

This bug also severely affects GHC on aarch64, and without disabling parallel building GHC is next to useless on that platform. Until a fix for that bug makes it into a release, it would be better to disable parallel builds on aarch64.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Fits CONTRIBUTING.md.

Copy link
Member

@peti peti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new code does not evaluate properly.

Also, please target this PR to the haskell-updates branch of Nixpkgs rather than master.

@TravisWhitaker
Copy link
Contributor Author

Closed in favor of #45313.

@peti
Copy link
Member

peti commented Aug 19, 2018

@TravisWhitaker, please don't close and re-create PRs for the exact same topic. Instead, please modify the existing PR so that the history etc. remains intact.

@TravisWhitaker
Copy link
Contributor Author

I am not aware of a way to change which branch an existing PR is asking to merge changes into.

@basvandijk
Copy link
Member

@TravisWhitaker press "Edit" besides the PR title then I believe a field becomes visible with which you can change the base. Then also make sure to rebase your branch on the new base and force-push it.

@TravisWhitaker
Copy link
Contributor Author

Ah thanks! That's really handy! Sorry for missing that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants