workaround to compile error and MAKEFLAGS from /etc/makepkg.conf #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to a known bug in ghc, make will always fail with `expectJust initTcInteractive` the first time you try to build it
Rather than setting them ourselves, we take the MAKEFLAGS from the systemwide configuration (at least on Arch)
neurocyte
added a commit
that referenced
this pull request
Feb 5, 2013
workaround to compile error and MAKEFLAGS from /etc/makepkg.conf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As Nathan points out, due to a known bug in ghc, you should run make twice in your script when building ghc. (it'll always fail with
expectJust initTcInteractivethe first time you try to build it fresh)Additional, since we're already somewhat arch-specific, we should source /etc/makepkg.conf to get the makeflags instead of using just -j6 (on my system I use -j12 for example) I was wondering why my load averages were so low before I realized you set -j manually.