This repository has been archived by the owner on Oct 7, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 206
Support Cabal 3.0.0.0 #1376
Labels
Comments
I'm afraid it still does not work with the current master:
Here's the full output: cabal-v2-fail.txt Before you ask -
Versions:
|
Current master does not support Cabal 3.0.0.0. EDIT: @mouse07410, your errors seem to me completely independent of Cabal 3 support. Installation of hie should work fine with cabal 3.0. |
What would you recommend me to do? UpdateUsing branch
|
Yes, please open a different issue. It might be MacOS specific. |
We are supporting Cabal 3.0.0.0 from #1126 on! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Recently Cabal 3.0.0.0 and cabal-install 3.0.0.0 was released, bringing along the following relevant changes I could find:
This change is relevant because the version of
cabal-helper
HIE is using still references these old symbols. upstreamcabal-helper
doesn't reference them anymore.cabal configure
is not using old-style builds anymore. This is a problem because bothcabal-helper
andghc-mod
have the assumption that old-style builds are the default in that they usecabal configure
and such, and notcabal v1-configure
.Relevant code in
ghc-mod
: https://github.com/alanz/ghc-mod/blob/910887b2c33237b703417ec07f35ca8bbf35d729/core/GhcMod/CabalHelper.hs#L192-L197.Relevant code in
cabal-helper
: https://github.com/alanz/cabal-helper/blob/eafed5e8c1d82b8daa35775b52361132f2e70261/src/CabalHelper/Compiletime/Compile.hs#L452As far as I can see, this results in HIE being broken for everybody using Cabal 3.0.0.0
Possible solutions
ghc-mod
andcabal-helper
to usev1-
commands explicitlycabal-helper
to not use the deprecated symbols anymore, by looking at what upstreamcabal-helper
did to remove them. This might be simple or it might not be simple at allcabal-helper
to the upstream version, this is what Use new cabal-helper #1245 tries to do, but there seems to be some problemsPing @fendor @bubba @alanz @mpickering @DanielG
Related issues:
The text was updated successfully, but these errors were encountered: