-
Notifications
You must be signed in to change notification settings - Fork 701
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
cabal-install 1.24 passes bad options to custom Setup #3433
Comments
Even worse with
|
essential information for reproducing this: /cc @dcoutts PS: this does not affect |
I'm having a similar issue when building
|
@23Skidoo you self-assigned this bug... are you working on this already? |
I haven't yet started, but I want to fix this before the release. |
I just had this error. I have been working on getting travis builds of Leksah working again. It is tricky because we need to test it with recent versions of Gtk+. So I have been playing with a The latest GHC 8.0.1 build worked (YAY). The GHC 7.10.3 build failed. Here is the error: |
Here is a
|
Changing Perhaps we should add |
I think that the error involving
cabal install -v2 base-noprelude --constraint 'Cabal == 1.18.*'
|
Previously, cabal always chose a Cabal library version to use for a package's setup script that didn't take setup-depends into account (cabalLibVersion). cabalLibVersion depended on the cabal-version field, the installed versions of Cabal, etc., and it was used when setup dependencies are not chosen by the dependency solver. When a package had a setup-depends, cabalLibVersion was later ignored in favor of the version chosen by the dependency solver. However, calculating the variable caused an error when the only suitable Cabal version was installed during the same install command (issue haskell#3436). It was also used to filter the configure flags (issue haskell#3433). This commit sets cabalLibVersion to the version chosen by the dependency solver, when possible.
Previously, cabal always chose a Cabal library version to use for a package's setup script that didn't take setup-depends into account (cabalLibVersion). cabalLibVersion depended on the cabal-version field, the installed versions of Cabal, etc., and it was used when setup dependencies were not chosen by the dependency solver. When a package had a setup-depends, cabalLibVersion was later ignored in favor of the version chosen by the dependency solver. However, calculating the variable caused an error when the only suitable Cabal version was installed during the same install command (issue haskell#3436). cabalLibVersion was also used to filter the configure flags (issue haskell#3433). This commit sets cabalLibVersion to the version chosen by the dependency solver, when possible.
Previously, cabal always chose a Cabal library version to use for a package's setup script that didn't take setup-depends into account (cabalLibVersion). cabalLibVersion depended on the cabal-version field, the installed versions of Cabal, etc., and it was used when setup dependencies were not chosen by the dependency solver. When a package had a setup-depends, cabalLibVersion was later ignored in favor of the version chosen by the dependency solver. However, calculating the variable caused an error when the only suitable Cabal version was installed during the same install command (issue haskell#3436). cabalLibVersion was also used to filter the configure flags (issue haskell#3433). This commit sets cabalLibVersion to the version chosen by the dependency solver, when possible. (cherry picked from commit 77fb0b9)
Previously, cabal always chose a Cabal library version to use for a package's setup script that didn't take setup-depends into account (cabalLibVersion). cabalLibVersion depended on the cabal-version field, the installed versions of Cabal, etc., and it was used when setup dependencies were not chosen by the dependency solver. When a package had a setup-depends, cabalLibVersion was later ignored in favor of the version chosen by the dependency solver. However, calculating the variable caused an error when the only suitable Cabal version was installed during the same install command (issue haskell#3436). cabalLibVersion was also used to filter the configure flags (issue haskell#3433). This commit sets cabalLibVersion to the version chosen by the dependency solver, when possible. (cherry picked from commit 77fb0b9)
NB:
base-noprelude-4.7.0.2
uses acustom-setup
stanzain this case, cabal-install-1.24 needs to talk to a custom
Setup.hs
compiled against Cabal-1.20:The text was updated successfully, but these errors were encountered: