[BUG] Build fails about accelerate HOT 6 CLOSED

Can you open bug reports for ansi-terminal and hashtables for this (and maybe link back here)? There isn't anything I can do about those dependencies..

from accelerate.

It's possible that deleting ~/.cabal wasn't enough to start fresh (deleting the files, but not informing GHC that they were deleted). The errors suggest running ghc-pkg check, which should list dependencies that were broken this way.
To fix them, I think you can run either ghc-pkg unregister <packageName> to remove them from the list, or reinstall them with cabal-install. I'm not sure there's an easy way to do this for all broken dependencies, outside of completely reinstalling GHC.

from accelerate.

What version of ghc is this with?

from accelerate.

This is The Glorious Glasgow Haskell Compilation System, version 8.10.2.

Can I do a completely sandboxed build? Isn't this what the v2-build command is supposed to do? ghc-pkg check only warns about missing haddocks.

EDIT: I tried to build ansi-terminal to reproduce the error and report it there, but it seems to work fine. At least, cabal install --lib ansi-terminal completes with Up to date.

EDIT2: The build with stack and the stack-8.10.yaml file works fine. I just wanted to use cabal in the first place.

from accelerate.

The v2-build command is sandboxed, but it isn't reproducible because Cabal still creates its own install plan (I think there is a way to fix that now though?) which looks like the problem you ran into. It's possibly when you tried cabal v2-build accelerate it decided a different install plan than when you installed ansi-terminal by itself. So you might be able to get cabal to work by installing the problematic dependencies one at a time, but from my experiences a long time ago (I gave up on cabal) that's also how you end up in cabal hell.

I'm going to close this because I think there is nothing we can do on our end, but if there is any way you think we can help please ask/let us know!

from accelerate.

Off-topic, but for reproducible builds with Cabal there's the index-state property in cabal.project to lock the dependency solving to a specific state of Hackage, and it's also possible to use one of Stackage's cabal.freeze files directly.

That beign said I have not had any issues building Accelerate with Cabal without doing any of that.

from accelerate.