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

Build fails with internal libraries that aren't dependencies #3996

Closed
KaneTW opened this issue Apr 29, 2018 · 5 comments
Closed

Build fails with internal libraries that aren't dependencies #3996

KaneTW opened this issue Apr 29, 2018 · 5 comments
Assignees

Comments

@KaneTW
Copy link

@KaneTW KaneTW commented Apr 29, 2018

Test case: https://github.com/KaneTW/stack-internal-lib-bug

cabal new-build succeeds.

@KaneTW
Copy link
Author

@KaneTW KaneTW commented Apr 29, 2018

There seems to be an issue with dependency resolution. Specifically, sublibs don't count as dependencies that have to be built.

Adding a dependency on every internal lib is a workaround.

@KaneTW KaneTW changed the title Build fails with multiple internal libraries Build fails with internal libraries that aren't dependencies Apr 29, 2018
@mihaimaruseac
Copy link
Contributor

@mihaimaruseac mihaimaruseac commented May 2, 2018

Thanks for the report. I was able to reproduce and I'll try to get a fix.

@mihaimaruseac
Copy link
Contributor

@mihaimaruseac mihaimaruseac commented May 21, 2018

Solved in #4033

@istathar
Copy link
Contributor

@istathar istathar commented May 22, 2018

Tested here. At first it failed (ie, no change) but it seemed to be using precompiled (thus buggy?) haddock-library artifacts. I manually nuked anything by that name in ~/.stack with find ~/stack -name 'haddock-library-*' -type d -print0 | xargs -0 rm --dontcopyandpastethis (which I'm sure was overkill) and although stack build works it is still failing for stack haddock.

Please re-open?

@mihaimaruseac
Copy link
Contributor

@mihaimaruseac mihaimaruseac commented May 22, 2018

There seems to be another bug regarding pre-existing artifacts. Will test that too and open an issue.

I haven't yet managed to get to stack haddock, it's in the plan for this week.

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
3 participants