Configuration for initial ghc lib dir #1378
Merged
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
wz1000
reviewed
Feb 15, 2021
wz1000
approved these changes
Feb 15, 2021
pepeiborra
force-pushed
the
getInitialGhcLibDir
branch
3 times, most recently
from
897cd59
to
ec14879
Compare
pepeiborra
force-pushed
the
getInitialGhcLibDir
branch
from
cd9f0f9
to
22529c2
Compare
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 discussed in #1375 the ghc lib dir used for initializing the unsafe dynflags needs to be configurable for clients that rely on custom session loading options