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 build with mtl^>=2.3 #19

Merged
merged 1 commit into from
Mar 13, 2024
Merged

Fix build with mtl^>=2.3 #19

merged 1 commit into from
Mar 13, 2024

Conversation

jorisdral
Copy link
Collaborator

@jorisdral jorisdral commented Feb 21, 2024

Apparently, without constraints the lib will pick mtl-2.2 on ghc-2.8. However, if we force the use of mtl-2.3, then we get compilation failures. This PR fixes those failures

$ cabal freeze --with-compiler="ghc-9.2.8"
$ cabal freeze --with-compiler="ghc-9.2.8" --constraint="mtl^>=2.3"
diff --git a/cabal.project.freeze b/cabal.project.freeze
index c11278a..443478a 100644
--- a/cabal.project.freeze
+++ b/cabal.project.freeze
@@ -15,14 +15,15 @@ constraints: any.QuickCheck ==2.14.3,
              any.data-array-byte ==0.1.0.1,
              any.deepseq ==1.4.6.1,
              any.directory ==1.3.6.2,
-             any.exceptions ==0.10.4,
+             any.exceptions ==0.10.7,
+             exceptions +transformers-0-4,
              any.filepath ==1.4.2.2,
              any.ghc-bignum ==1.2,
              any.ghc-boot-th ==9.2.8,
              any.ghc-prim ==0.8.0,
              any.hashable ==1.4.3.0,
              hashable +integer-gmp -random-initial-seed,
-             any.mtl ==2.2.2,
+             any.mtl ==2.3.1,
              any.optparse-applicative ==0.18.1.0,
              optparse-applicative +process,
              any.pretty ==1.1.3.6,

@jorisdral jorisdral self-assigned this Feb 21, 2024
@jorisdral jorisdral requested a review from edsko February 21, 2024 19:51
@jorisdral jorisdral merged commit feca60c into main Mar 13, 2024
12 checks passed
@jorisdral jorisdral deleted the jdral/fix-mtl-2.3 branch March 13, 2024 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant