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

Fix GHC 810 rc1 build #317

Closed
wants to merge 3 commits into from

Conversation

Avi-D-coder
Copy link

Test dependencies do not build.

@googleson78 googleson78 self-assigned this Feb 12, 2020
@KingoftheHomeless KingoftheHomeless mentioned this pull request Feb 13, 2020
@isovector
Copy link
Member

What's the state of this?

@Avi-D-coder
Copy link
Author

no idea. haven't checked if any of the test deps are upgraded to 8.10

@googleson78
Copy link
Member

How do you build from this branch?
Running

git clean -fdx
stack build --stack-yaml stack810.yaml

results in a lot of stuff like this

Warning: Failed to decode module interface: /home/googleson78/git/polysemy/.stack-work/dist/x86_64-linux-tinfo6/Cabal-3.2.0.0/build/Polysemy/Internal/Writer.hi Decoding failure:
         Invalid magic: e49ceb0f

@Avi-D-coder
Copy link
Author

@googleson78 See commercialhaskell/stack#5134

@sorki
Copy link

sorki commented May 21, 2020

FWIW to build on NixOS I've only had to use polysemy-research/loopbreaker#11

Missed that it mainly fixes polysemy-plugin which is still needed.

@TheMatten
Copy link
Collaborator

TheMatten commented Jul 29, 2020

Is this PR still relevant? Because polysemy builds for me on current nightly snapshot (8.10.1) just fine, except for dump-core flag (but that seems to be upstream issue - edit: yav/dump-core#9).

@TheMatten TheMatten added waiting on upstream requires upstream patches first enhancement New feature or request labels Jul 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request waiting on upstream requires upstream patches first
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants