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

Adjust -i paths used by ghci to point to autogen / etc files generated by newer Cabal #3791

Closed
mgsloan opened this issue Jan 18, 2018 · 5 comments

Comments

@mgsloan
Copy link
Contributor

@mgsloan mgsloan commented Jan 18, 2018

I think this change was introduced in Cabal >= 2. stack ghci currently adds dist/build/autogen and similar dirs to the source search path. Cabal's per component build instead puts them in dist/build/$COMPONENT/autogen.

@gahag
Copy link

@gahag gahag commented Jan 20, 2018

This also affects flycheck for emacs. It reports it can't find autogen modules, as stack ghci does. Downgrading the resolver from lts-10.3 to lts-9.21 seems to be a temporary solution.

gahag added a commit to gahag/FSQL that referenced this issue Jan 20, 2018
The latest version of stack has a small incompatibility with the
latest version of cabal.
Refer to commercialhaskell/stack#3791
mgsloan added a commit that referenced this issue Jan 20, 2018
@mgsloan
Copy link
Contributor Author

@mgsloan mgsloan commented Jan 20, 2018

@gahag I've opened a PR which fixes this - #3795

mgsloan added a commit that referenced this issue Jan 20, 2018
mgsloan added a commit that referenced this issue Jan 20, 2018
sergv added a commit to sergv/flycheck-haskell that referenced this issue Jan 22, 2018
mgsloan added a commit that referenced this issue Feb 11, 2018
mgsloan added a commit that referenced this issue Feb 18, 2018
mgsloan added a commit that referenced this issue Feb 18, 2018
@dbaynard
Copy link
Contributor

@dbaynard dbaynard commented Mar 15, 2018

Is this supposed to fix stack ghci for libraries with internal library modules? (If not, I'll open a new issue).

Edit: #3795 does fix it spoke too soon. I'll investigate further.

@borsboom
Copy link
Contributor

@borsboom borsboom commented Apr 4, 2018

@mgsloan Does this still need to be a blocking issue? Hoping to get 1.7 out the door before too long.

mgsloan added a commit that referenced this issue Apr 9, 2018
@mgsloan
Copy link
Contributor Author

@mgsloan mgsloan commented Apr 9, 2018

I think it would be good to merge #3795 before the release. Shoudla merged it earlier for more testing, but hey. I've pushed a rebased version, will merge after that passes CI.

mgsloan added a commit that referenced this issue Apr 10, 2018
…-3791

Use per-component build directories for ghci with Cabal>=2.0 #3791
@mgsloan mgsloan closed this Apr 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants