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

Ignoring stack-built ghc executables when looking for compiler for Setup.hs (#1052). #1210

Merged
merged 1 commit into from Oct 22, 2015

Conversation

mwu-tow
Copy link
Contributor

@mwu-tow mwu-tow commented Oct 21, 2015

The issue #1052 was once fixed but got broken again when compiling custom Setup.hs has been implemented — see #1052 (comment). This PR fixes this by excluding local extra bin directories from lookup when searching for GHC to compile Setup.hs with.

-- https://github.com/commercialhaskell/stack/issues/1052
menvWithoutLocals <- liftIO $ configEnvOverride config envSettings { esIncludeLocals = False }
getGhcPath <- runOnce $ liftIO $ join $ findExecutable menvWithoutLocals "ghc"
getGhcjsPath <- runOnce $ liftIO $ join $ findExecutable menvWithoutLocals "ghcjs"
Copy link
Contributor

Choose a reason for hiding this comment

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

@mgsloan Can you confirm if the local database should or shouldn't be used for finding the ghcjs executable?

Copy link
Contributor

Choose a reason for hiding this comment

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

Right, it makes sense to exclude locals for resolving the ghcjs binary as well.

snoyberg added a commit that referenced this pull request Oct 22, 2015
Ignoring stack-built `ghc` executables when looking for compiler for Setup.hs (#1052).
@snoyberg snoyberg merged commit 8ea675e into commercialhaskell:master Oct 22, 2015
@snoyberg
Copy link
Contributor

Merged, thanks!

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

Successfully merging this pull request may close these issues.

None yet

3 participants