-
Notifications
You must be signed in to change notification settings - Fork 20
Cabal build is not working for me #746
Comments
I've not been following along about how we got here, but why are we using cabal for the examples? |
Can you tell me your Haskell version |
That's probably it, then -- I have version 8.8.4. That's also the latest version on the gLinux package manager, though, and I'd prefer not to have to maintain a from-source installation if possible. |
There are definitely some benefits to using cabal:
The cabal changes will be easiest to roll back if there are usability issues, but i expect things to be simpler going forward (after potentially some speed bumps such as this). In the long run I still see us potentially removing Haskell and moving all logic to Coq. I'd like to make a few more changes to simplify our source tree in #742 such that we only have source/project files in our source tree and artefacts/compilation objects are put into other directories (dune being the simplest way to achieve this for Coq). That in turn will simplify browsing through the directory hierarchy but also more tangible benefits like simplifying our makefile building and cleaning rules. |
Let me relax the constraints in the cabal files, we should be fine with 8.8.4 |
that doesn't seem to fix it: running
|
I think it's a different issue -- my issue was fixed by #749, and this one is telling you it can't find A |
Yep, I was just using the wrong |
I don't know if I have the wrong cabal version or a missing dependency (
base
?), but after a checkout ofmain
and amake clean
I get this error from the cava haskell target:The text was updated successfully, but these errors were encountered: