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
haddock-library's internal attoparsec library cannot be found - broken package #4071
Comments
Probably I missed something, I'll take a look. |
@mihaimaruseac Awesome, thanks!! |
I have the same issue.
|
I was able to reproduce it even on
First, I build it once on a snapshot which is not existing on my computer:
Then, I rebuild it, with no actions in between:
All is rebuild, as expected from Stack before 1.7. Now, if I switch resolver to the next one.. failure:
So, I definitely missed something in #3955, but I have an intuition of where. Hopefully I can solve this this weekend. |
Deleting stack/src/Stack/Build/Execute.hs Lines 1500 to 1518 in 2dfafed
Sure, there might be an error when reading from the precompiled cache too, I'll look into that once I finalize this. Luckily, I was already working on this for #3787 (caused by a similar lack of symmetry between handling internal libraries and the main library). |
I confirm, it works. Thanks for the workaround @mihaimaruseac, I hope you’ll be able to fix that error. ❤️ |
I think I have a fix. I'll test it later this week, get some integration tests and then put the PR which fixes several internal libraries bugs. Probably around the weekend. |
Solved by #4111 |
Thanks, you rock! 😗 |
The fix for commercialhaskell/stack#4071 isn't totally working. See https://circleci.com/gh/pbrisbin/yesod-markdown/221. It seems that the Build step didn't re-use the dependencies from the Dependencies step, so it tripped over haddock-library since we don't remove the precompiled file there (like we do in Setup). I could add that removal there to but that would guarantee that the two steps will duplicate work.
The fix for commercialhaskell/stack#4071 isn't totally working. See https://circleci.com/gh/pbrisbin/yesod-markdown/221. It seems that the Build step didn't re-use the dependencies from the Dependencies step, so it tripped over haddock-library since we don't remove the precompiled file there (like we do in Setup). I could add that removal there to but that would guarantee that the two steps will duplicate work.
I'm still getting this error on Windows with
And the workaround of "Deleting |
I think this is different, as you're getting the error due to haddock. |
See #4195 |
General summary
On the development version of stack, I am encountering build issues with haddock-library.
#3899 is a related issue about the caching of internal library dependencies. In particular, it is the same context where I am running into an issue, hakyll's dependency on haddock-library.
Steps to reproduce
stack --resolver lts-11.11 build hakyll
Expected
Actual
(Note, this log is from a re-run of the build, after doing a full build)
Stack version
(the repo dirtyness is an extra file or two that do not affect compilation)
Method of installation
Installed via
stack install
in latest git repo.Attempted workaround
I reasoned that this may well be a
Cabal
bug, but I could not straightforwardly test this hypothesis, becausestack setup --upgrade-cabal
did not work forCabal-2.2.0.1
+ghc-8.2.2
. I have opened #4070 to track this.Successful workaround
The workaround described here worked for my actual project (the repro above is a minimal one). So, instead I have
The text was updated successfully, but these errors were encountered: