Using Cabal-1.22 for Setup.hs with GHC-7.8 #1002
Comments
There's an --upgrade-cabal argument to stack setup that should do what you Can we move this q&a to stack overflow so that others can find this answer On Thu, Sep 17, 2015, 2:03 PM Michał Wawrzyniec Urbańczyk <
|
@snoyberg I'm not sure if it will work for me. I use a custom (patched) GHC 7.8.4 build, the GHC downloaded by
Apparently it failed. And so it is — |
That may be a bug on Windows, quite unrelated. Let me check something. |
Can you try upgrading to stack master ( |
I tried My current |
Looks like you're hitting the 32k character limit on Windows... try this executable instead. https://s3.amazonaws.com/download.fpcomplete.com/michael/stack-f24a2474b06722244acae2b3159be819cda6bb20.zip |
Thanks. Could it be cause my GHC is 64-bit and stack you provided is 32-bit and stack tries to install GHC with the same architecture? Can I somehow tell |
There's a |
Oh, right, sorry about that — I'm still getting started with stack. It works! Now my package builds correctly. |
Sure, no problem, glad it's working! On Thu, Sep 17, 2015 at 3:18 PM, Michał Wawrzyniec Urbańczyk <
|
Hello,
I have a package that uses custom
Setup.hs
file that requires Cabal library at least in version 1.22. I need to build the package with GHC 7.8.With
cabal
it is enough tocabal install cabal
— and thenSetup.hs
will be linked against the latest Cabal library. Using GHC 7.8 with it works seamlessly.How can I tell
stack
to use newer Cabal version forSetup.hs
?I tried adding
Cabal-1.22.4.0
to theextra-deps
field but it does not help — apparently the newer Cabal will be available to the built package but not itsSetup.hs
. It still getsCabal-1.18.1.5
that comes with GHC 7.8.The text was updated successfully, but these errors were encountered: