-
Notifications
You must be signed in to change notification settings - Fork 842
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
stack ghci
does not recognise internal libraries
#3926
Comments
This comment looks like it is relevant: Line 592 in d1c40ae
|
I can confirm #3795 does not fix this (still broken in current master) and further to @gbaz's comment, it appears to be a more fundamental design issue. (Also, I never new about the permalinks to code snippets — thanks! It doesn't really afford scrolling when it overflows, though, at least in chrome, as happens here.) stack/src/Stack/Types/NamedComponent.hs Lines 22 to 34 in 979e613
|
I think #3955 can help here but didn't test yet. |
I tested now and still gets the same error. I'll investigate more during this week. |
I managed to get rid of the |
I'm there too, hope to get some progress today or next weekend at BayHac. |
It seems that the difference between |
I've compared command lines and this is what we need to pass:
I've also seen |
Ugh. So after getting stack to output that, I find out that cabal new-build generates
which are required. So that doesn't work. Going to take a look what stack does with sublibs. E: ok, good, it does something similar
|
PR that fixes this is up. I need to write some test cases, though. |
You got it ahead of me, but I see I was approaching it from a different angle, making more complex changes. I'll get my PR submitted too as it also handles rebuilding from scratch and tracks changes in sublibraries. I'm testing now the integration tests but will have something up and running in a few hours. |
This was done in #3982 but I forgot to close it. |
I'm still running into this issue:
|
You mean #4564, the issue with all the updates? |
Yes, my bad, just updated it. |
I need to find cycles to work on that :( |
Relates to #3795 (and #3791) and also #3288.
I suspect the fix is to reproduce whatever #3288 did for the
build
command but forghci
.Steps to reproduce
Easiest to check out dbaynard/issues@2530d18 (internal-libraries branch) and run
stack ghci
.Alternatively, create a package which has an internal library module and attempt to import that into that package's own library or an executable (they have the same outcome).
Expected
stack ghci
loads the repl.Actual
Error message, for internal library named
internal
Note,
stack build
is successful. Also,stack exec -- ghci
loads correctly (though doesn't load the packages).The full output is in the readme in the
internal-libries
directory at the dbaynard/issues github repo, above.Stack version
I merged fix-ghci-autogen-path-3791 (030a442) into master (
27894ff) for the test.
Method of installation
From git repo — see above
The text was updated successfully, but these errors were encountered: